From: Kevin Buettner <kev@primenet.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] Re: gdb null ptr
Date: Fri, 03 Nov 2000 21:32:10 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590678205651@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590678205647@msgid-missing>
On Nov 3, 8:32am, Pete Wyckoff wrote:
> wilson@cygnus.com said:
> > I don't see how this can happen from looking at the source. We only cache
> > a type in dwarf2_cached_types if it has a DW_AT_name attribute, and if it
> > does have such an attribute, then the type should have a name or tag name.
> >
> > Can you provide me with a testcase? A binary that I can run under gdb should
> > be sufficient. You could put it in ftp.cygnus.com/incoming and then mail
> > the file name to me.
> >
> > Since this doesn't appear to be an ia64 specific problem, if I don't have a
> > testcase then I will just punt to the gdb developers
> > http://sources.redhat.com/gdb/#bugs
>
> It may very well be a gdb bug. Anyway, I put a huge executable in
> the incoming dir as pw-gdb-bug-ex.
>
> 3078a3f848cba6d1f76fbfe3707b0464 pw-gdb-bug-ex
Peter,
Thanks for sending us this test case.
I think this problem is arising because the dwarf2 reader had
problems earlier on. I.e, I see
During symbol reading, non-constant array bounds form 'DW_FORM_ref4' ignored.
During symbol reading, unsupported tag: 'DW_TAG_constant'.
My guess is that when these (at the moment) unsupported cases arise,
the reader fails to properly initialize a name or tag name.
I'll look into it some more and get back to you when I understand the
problem better.
Thanks again,
Kevin
next prev parent reply other threads:[~2000-11-03 21:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-03 2:19 [Linux-ia64] Re: gdb null ptr Jim Wilson
2000-11-03 13:32 ` Pete Wyckoff
2000-11-03 21:32 ` Kevin Buettner [this message]
2000-11-03 21:42 ` Jim Wilson
2000-11-03 23:02 ` Kevin Buettner
2000-11-04 3:20 ` Daniel Berlin
2000-11-07 22:28 ` Jim Blandy
2000-11-07 23:38 ` Daniel Berlin
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=marc-linux-ia64-105590678205651@msgid-missing \
--to=kev@primenet.com \
--cc=linux-ia64@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.