Re: GDB 6.8 on sparc64-linux not working, idem on powerpc64-linux

[Laurent GUERBY <laurent@guerby.net>]

On Sat, 2009-02-28 at 14:31 +0100, Laurent GUERBY wrote:
> On Sat, 2009-02-28 at 14:02 +0100, Mark Kettenis wrote:
> > > From: Laurent GUERBY <laurent@guerby.net>
> > > Date: Sat, 28 Feb 2009 13:36:52 +0100
> > > 
> > > (gdb) b main
> > > Breakpoint 1 at 0x1000044c: file toto.c, line 1.
> > > (gdb) r
> > > Starting program: /home/guerby/tmp/a.out 
> > > warning: no loadable sections found in added symbol-file system-supplied DSO at 0x100000
> > > 
> > > Program received signal SIGTRAP, Trace/breakpoint trap.
> > > 0x1000044c0002d032 in ?? ()
> > > (gdb) bt
> > > #0  0x1000044c0002d032 in ?? ()
> > > #1  0x0007d5a400000000 in ?? ()
> > > Cannot access memory at address 0xfffff4f010018940
> > > (gdb) n
> > > Cannot find bounds of current function
> > 
> > This (and the sparc64 issue) smells like a mismatch between bitness of
> > gdb and the program you're trying to debug.  What does file(1) report
> > when you run it on your gdb binary and your program's binary?
> 
> I built GDB as 32 bits indeed, I thought the host choice would not impact
> the target debugability but it looks like I was wrong. I'm not
> familiar (yet) with the GDB documentation, is this mentionned somewhere?
> 
> On powerpc64 rebuilding as 64 bits cured the issue, on sparc64 I will
> report soon.

On sparc64 and mips64el it worked fine too.

Sincerely,

Laurent