Seg fault with mcrypt?
| From: | Mitch Vincent | Date: | Fri, 25 Jun 1999 23:46:18 +0000 |
| Subject: | Seg fault with mcrypt? | ||
| Groups: | php.dev | ||
| Request: | Send a blank email to php-dev+get-7568@lists.php.net to get a copy of this message | ||
Redhat 6.0, Kernel 2.2.9
Apache 1.3.6, PHP 3.0.10
It seems anytime I urlencode, then mcrypt a string and try to urldecode and
mcrypt_decrypt it, most of the time in a different script after passing the
encrypted strings over a URL, I get a segfault. I say most of the time
because it has happened in many different situations. I thought at frst it
was something I was doing, but finally decided to submit a bug report to see
if you guys could see anything..
If I don't use mcrypt, I never see any problems.
Backtrace:
#0 0x400c5111 in __kill ()
#1 0x400c4d66 in raise (sig=6) at ../sysdeps/posix/raise.c:27
#2 0x400c6447 in abort () at ../sysdeps/generic/abort.c:88
#3 0x400bee8e in __assert_fail () at assert.c:59
#4 0x80646ce in strcpy ()
#5 0x80a20b9 in strcpy ()
#6 0x80a2188 in strcpy ()
#7 0x8064719 in strcpy ()
#8 0x8064992 in strcpy ()
#9 0x80a6819 in strcpy ()
#10 0x80afe07 in strcpy ()
#11 0x80b05f3 in strcpy ()
#12 0x400becb3 in __libc_start_main (main=0x80b02cc <strcpy+410308>,
argc=1, argv=0xbffffd74, init=0x804b068 <_init>,
fini=0x814076c <_fini>, rtld_fini=0x4000a350 <_dl_fini>,
stack_end=0xbffffd6c) at ../sysdeps/generic/libc-start.c:78
If this isn't of any use, I apologise. I used gdb, the server executable
and the core file to generate this per the instructions on the bug report
page.
Thanks!
-Mitch
"When all your plans fail, backup, re-group and press on. The only real
failure is quitting..."