On Sat, May 22, 2004 at 01:05:23PM +1000, Christopher Lee wrote: > Hi Andrew, > > Here's the results:-
Okay, doesn't mean so much to me, but it might help someone. > > [snipped out most of the above symbols messages] > Reading symbols from /usr/lib/asterisk/modules/format_g726.so...done. > Loaded symbols for /usr/lib/asterisk/modules/format_g726.so > Reading symbols from /usr/lib/asterisk/modules/format_g729.so...done. > Loaded symbols for /usr/lib/asterisk/modules/format_g729.so > Reading symbols from /usr/lib/asterisk/modules/codec_g729a.so...done. > Loaded symbols for /usr/lib/asterisk/modules/codec_g729a.so > #0 0x4044e862 in lsp_get_quant () > from /usr/lib/asterisk/modules/codec_g729a.so > (gdb) bt > #0 0x4044e862 in lsp_get_quant () > from /usr/lib/asterisk/modules/codec_g729a.so > #1 0x00000000 in ?? () > (gdb) x/5i $eip > 0x4044e862 <lsp_get_quant+210>: fcomi %st(5),%st > 0x4044e864 <lsp_get_quant+212>: jbe 0x4044eb40 <lsp_get_quant+944> > 0x4044e86a <lsp_get_quant+218>: fsubr %st,%st(2) > 0x4044e86c <lsp_get_quant+220>: faddp %st,%st(1) > 0x4044e86e <lsp_get_quant+222>: fxch %st(1) prehaps try info registers st0 st1 st2 st3 st4 st5 st6 st7 as well, that said I'm not overly familar with those floating point instructions. http://nasm.sourceforge.net/doc/html/nasmdoc0.html > (gdb) info registers > eax 0x3 3 > ecx 0x3c 60 > edx 0x1 1 > ebx 0x15 21 > esp 0xbfffeef0 0xbfffeef0 > ebp 0xbfffef10 0xbfffef10 > esi 0x40459d40 1078304064 > edi 0x40458940 1078298944 > eip 0x4044e862 0x4044e862 > eflags 0x10202 66050 > cs 0x23 35 > ss 0x2b 43 > ds 0x2b 43 > es 0x2b 43 > fs 0x2b 43 > gs 0x2b 43 > fctrl 0x37f 895 > fstat 0x1132 4402 > ftag 0x400f 16399 > fiseg 0x23 35 > fioff 0x4044e860 1078257760 > foseg 0x2b 43 > fooff 0x0 0 > ---Type <return> to continue, or q <return> to quit--- > fop 0xcc 204 > mxcsr 0x1f80 8064 > orig_eax 0xffffffff -1 > (gdb) > > And re the F00F bug, yep I figured it was probably very unlikely to be the > root cause of the problem, as I have noticed messages when linux boots that > it implements a workaround for the bug, so if that's the case then I guess > all should be fine. > > Thanks, > Chris Lee > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of > [EMAIL PROTECTED] > Sent: Saturday, 22 May 2004 12:46 PM > To: [EMAIL PROTECTED] > Subject: Re: [Asterisk-Users] G.729a beta codec on old Pentiums > > If you have gdb installed, try gdb /usr/sbin/asterisk (or whichever path is > appropiate) name_of_core_file, and send back the results of > > bt > x/5i $eip > info registers > > and that should allow the developers or other people to work out what the > problem is. > > As for the f00f bug, its unlikely that would be causing problems, the > mention of f00f is there so that you can check to see if the machine is > vulnerable. From memory, most os's now include work arounds for that bug. > > > _______________________________________________ > Asterisk-Users mailing list > [EMAIL PROTECTED] > http://lists.digium.com/mailman/listinfo/asterisk-users > To UNSUBSCRIBE or update options visit: > http://lists.digium.com/mailman/listinfo/asterisk-users _______________________________________________ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
