This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: m68k bootstrapping broken
Richard Zidlicky wrote:
On Wed, Jan 14, 2004 at 12:33:55AM +0100, Bernardo Innocenti wrote:
I usually use -ggdb. GDB 6.0 still has some problems with the
ColdFire BDM target, so I'm primarly using 5.3. I vaguely recall
seeing correct backtraces in the uClinux kernel, which is compiled
by default with -fomit-frame-pointer. But perhaps
linux kernel is a special case, do you use gdb to debug it?
Yes, I do: I connect to my target board with a BDM pod. GDB can
load the kernel image in RAM and debug it. Even in interrupts! ;-)
Code compiled with -ggdb definitely does not have correct
baktrace here.
I'll retest. What specific gdb version were you using again?
I'm mostly using gdb 5.3 targeted at m68k-elf (well, actually
it's m68k-bdm-elf). I gave 6.0 a shot but I had several problems.
`-O' also turns on `-fomit-frame-pointer' on machines where doing
so does not interfere with debugging.
well afaics it does heavilly interfere with debugging on m68k.
If so, we shouldn't enable it, at least not for m68k-linux. It's
most probably a bug or limitation in gdb, because the dwarf2 debug
info should be enough to do backtraces and inspect variables in the
frame.
--
// Bernardo Innocenti - Develer S.r.l., R&D dept.
\X/ http://www.develer.com/