Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: Maxim Grigoriev <maxim@tensilica.com>
Cc: gdb@sourceware.org, Bob Wilson <bwilson@tensilica.com>,
		Marc Gauthier <marc@tensilica.com>
Subject: Re: GDB (mis)behavior depends on DWARF DW_TAG_compile_unit data
Date: Mon, 12 Mar 2007 21:23:00 -0000	[thread overview]
Message-ID: <20070312212405.GM14401@adacore.com> (raw)
In-Reply-To: <45F5C0D3.90002@hq.tensilica.com>

> If you think it's a generic GDB problem I can fix it. I have to fix it
> anyway on Xtensa GDB. I don't see how it can be Xtensa-specific.
> Xtensa GCC compiler DWARF is consistent with native GCC 4.1.1 compiler
> on my Linux box.  So if this is a compiler problem ( which I doubt )
> it seems to be pretty generic.

With the information you have given us, all I can say is that GDB
should be able to handle the situation, so we do have a bug somewhere.
Whether it is in GCC or GDB is still an open question as far as I can
tell.

Have you checked the line-table as well in both cases? There is
a very convenient command that gives you the list of lines known
by GDB for any given file: -symbol-list-lines. It's a MI command,
but you should be able to use it from the GDB prompt using
"interpreter-exe mi -symbol-list-lines" followed by the filename.

-- 
Joel


  reply	other threads:[~2007-03-12 21:23 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-12 20:33 Maxim Grigoriev
2007-03-12 20:49 ` Daniel Jacobowitz
2007-03-12 21:06   ` Maxim Grigoriev
2007-03-12 21:23     ` Joel Brobecker [this message]
2007-03-12 21:54       ` Maxim Grigoriev
2007-03-12 21:58         ` Daniel Jacobowitz
2007-03-15  2:03           ` Maxim Grigoriev
2007-03-12 20:57 ` Bob Wilson

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=20070312212405.GM14401@adacore.com \
    --to=brobecker@adacore.com \
    --cc=bwilson@tensilica.com \
    --cc=gdb@sourceware.org \
    --cc=marc@tensilica.com \
    --cc=maxim@tensilica.com \
    /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