|
From: Konstantin S. <kon...@gm...> - 2009-02-06 13:08:33
|
Just checking: the mechanism used to get stack traces in exp-ptrcheck will *not* be confused by such hand-written assembly, right? --kcc On Fri, Feb 6, 2009 at 3:58 PM, Konstantin Serebryany <kon...@gm...> wrote: >> You need to check that GDB can unwind from that specific instruction, >> not just from somewhere inside the function. Since the page number >> will be different, but the page offset will be the same, you need to >> get GDB to the instruction whose lowest 12 bits is 0x140 (since >> Valgrind reports 0xC32B140) and see if you can unwind from there. > > Indeed... > If I break at the function in gdb, I can get the stack trace. > But after typing 'n' several times, I loose this ability. > wow! > > --kcc > |