From: Laurent GUERBY <laurent@guerby.net>
To: Mark Kettenis <mark.kettenis@xs4all.nl>
Cc: gdb@sourceware.org
Subject: Re: GDB 6.8 on sparc64-linux not working, idem on powerpc64-linux
Date: Sat, 28 Feb 2009 13:31:00 -0000 [thread overview]
Message-ID: <1235827903.11347.484.camel@localhost> (raw)
In-Reply-To: <200902281302.n1SD26n5020357@brahms.sibelius.xs4all.nl>
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.
Thanks for your help!
Laurent.
next prev parent reply other threads:[~2009-02-28 13:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-28 9:14 GDB 6.8 on sparc64-linux not working Laurent GUERBY
2009-02-28 12:37 ` GDB 6.8 on sparc64-linux not working, idem on powerpc64-linux Laurent GUERBY
2009-02-28 13:02 ` Mark Kettenis
2009-02-28 13:31 ` Laurent GUERBY [this message]
2009-03-01 15:09 ` Laurent GUERBY
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1235827903.11347.484.camel@localhost \
--to=laurent@guerby.net \
--cc=gdb@sourceware.org \
--cc=mark.kettenis@xs4all.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox