From: Jeremy S. <js...@mv...> - 2001-08-17 16:51:05
|
I suspect the odd fpscr displayed is due to a broken GDB, or at least one with register number identifiers that are inconsistent with the kernel/ptrace... mine behaves the same way (at the moment). [BTW, we see the same thing, and we're using glibc 2.2.3.] --Jeremy Siegel kaz Kojima wrote: > "Bao C. Ha" <ba...@se...> wrote: > > It still crashed when $fpscr was set to 0x80004 > > > > (gdb) p/x $fpscr=0x80004 > > $2 = 0x80004 > > (gdb) p/x $fpscr > > $3 = 0x80004 > > (gdb) c > > Continuing. > > > > status=%x > [snip] > > Hmm... I have no idea for the real problem at this point. Anyway, > 0x3f737871 is very broken if gdb works correctly and it seems > that some bad things occur in shared library. Perhaps, rebuilding > libc with gcc -O may be not so bad idea. > > kaz > > _______________________________________________ > linuxsh-dev mailing list > lin...@li... > http://lists.sourceforge.net/lists/listinfo/linuxsh-dev |