Hi, YAMAMOTO, Hiroyuki, le Mon 05 Mar 2007 23:48:37 +0900, a écrit : > Samuel Thibault wrote: > >Ah, yes, the report is older than that, but let's see if fixing #396741 > >fixes yours. > > > > I compiled today's CVS version with --enable-kdb, and succeeded in the > reproduction of the phenomenon. > > db>trace > 0x10d577(2edabc,10379000,2eecc4,173b99,ff007b8) > 0x133dae(ff007b8,10379000,588,1,1080) > 0x173b99(572c8,4,2eecf4,202,2b7480) > 0x1b4b18(562c0,0,9,2eed3c,2eed8c) > 0x1b557b(9,2b7480,2eed64,11f6f4,fef5ca0) > 0x15a3b0(9) > 0x1377f5(2edabc,1036e000,11a86ee0,1738bb,ff007b8) > 0x133dae(ff007b8,1036e000,38,1,0,11a86f24,1036e070,da,1036e010,ff43274,2b7480,562c0,1036e000,12,103c7960) > 0x1738bb(ff007b4,103c7960,12,8,0) > 0x140884(1039e9e4,103d1010,0,8000000a,ff43274) > 0x11a974(1039e9d4,103b60f4,103b5844,0,0) > 0x14bc13(125fd04,3,38,28,2c) > Bad frame pointer: 0x125fce0
Could you run gdb gnumach and type gdb> l * 0x10d577 etc for the first number of each line? Thanks, Samuel
