Messages in this thread | | | Date | Wed, 21 Jan 2004 15:14:59 -0800 | From | George Anzinger <> | Subject | Re: KGDB 2.0.3 with fixes and development in ethernet interface |
| |
Daniel Jacobowitz wrote: > On Wed, Jan 21, 2004 at 07:16:48PM +0530, Amit S. Kale wrote: > >>Now back to gdb problem of not being able to locate registers. >>schedule results in code of this form: >> >>schedule: >>framesetup >>registers save >>... >>... >>save registers >>change esp >>call switchto >>restore registers >>... >>... >> >>GDB can't analyze code other than frame setup and registers save. It may not >>show values of variables that are present in registers correctly. This used >>to be a problem some time ago (gdb 5.X). Perhaps gdb 6.x does a better job. >>hmm... >>May be its time I should look at gdb's x86 register info code again. > > > You should try GDB 6.0, which will use the dwarf2 unwind information to > accurately locate registers in any GCC-compiled code with -gdwarf-2 (-g > on Linux targets). > > As George is now painfully familiar with :)
Well, some of that may be in asm code which may need help. Need to check this. >
-- George Anzinger george@mvista.com High-res-timers: http://sourceforge.net/projects/high-res-timers/ Preemption patch: http://www.kernel.org/pub/linux/kernel/people/rml
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |