From: Albert Chin <gdb@mlists.thewrittenword.com>
To: gdb@sourceware.org
Subject: Re: SEGV running gdb-6.7 on Tru64 UNIX 5.1
Date: Thu, 18 Oct 2007 16:52:00 -0000 [thread overview]
Message-ID: <20071018165236.GA90995@mail1.thewrittenword.com> (raw)
In-Reply-To: <20071018031954.GN16618@adacore.com>
On Wed, Oct 17, 2007 at 08:19:54PM -0700, Joel Brobecker wrote:
> > Anyone running 6.7 successfully on Tru64 UNIX 5.1? gdb-6.6 Worked ok.
>
> I am able to run it through your example. However, I did build the
> executable using gcc, not cc. That's probably where the difference is.
I built with gcc-3.4.3 and still get a SEGV with the 'list' command,
but the ladebug backtrace is different:
>0 0x1200a802c in target_write_with_progress(ops=0x1401297c0, object=TARGET_OBJECT_SPU, annex=0x0, buf=0x0, offset=4831842700, len=4831819312, progress=0x11fffb6b0, baton=0x11fffb630) "target.c":1452
#1 0x1200a7ff4 in target_write_with_progress(ops=0x1401297c0, object=TARGET_OBJECT_SPU, annex=0x0, buf=0x0, offset=4831842700, len=4831819312, progress=0x11fffb6b0, baton=0x11fffb630) "target.c":1439
> > >0 0x120125920 in symbol_found(funfirstline=1, canonical=0x0, copy=0x1401778d0="main", sym=0x14014d7c0, file_symtab=0x0, sym_symtab=0x0) "linespec.c":1786
>
> The problem here is that both file_symtab and sym_symtab are NULL.
> Looking at the frame just above it:
>
> > #1 0x120125744 in decode_variable(copy=0x1401778d0="main", funfirstline=1, canonical=0x0, file_symtab=0x0, not_found_ptr=0x0) "linespec.c":1737
>
> Apparently, lookup_symbol found a symbol for "main", but did not
> return the associated symtab.
>
> You'll probably need to debug GDB to find out why
> lookup_symbol_in_language set the symtab to NULL...
Ok, I'll have to do some digging. Thanks.
--
albert chin (china@thewrittenword.com)
prev parent reply other threads:[~2007-10-18 16:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-17 23:38 Albert Chin
2007-10-18 3:20 ` Joel Brobecker
2007-10-18 16:52 ` Albert Chin [this message]
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=20071018165236.GA90995@mail1.thewrittenword.com \
--to=gdb@mlists.thewrittenword.com \
--cc=gdb@sourceware.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).