From: Daniel Jacobowitz <drow@false.org>
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 20:49:00 -0000 [thread overview]
Message-ID: <20070312204857.GA20515@caradoc.them.org> (raw)
In-Reply-To: <45F5B929.3050406@hq.tensilica.com>
On Mon, Mar 12, 2007 at 01:33:45PM -0700, Maxim Grigoriev wrote:
> Hello members,
>
> I would like to hear your opinion on whether what I see is a compiler
> problem or a GDB misbehavior.
>
> GDB session goes wrong, if my test case is compiled using a base name as a
> source file. Everything is fine, when an absolute path name is used
> instead. I checked several compilers ( all GCCs ). They seem to be
> consistent in generating DWARF DW_TAG_compile_unit information in this case.
>
> Anyway, even if GDB treats this situation as a bad DWARF data it doesn't
> look decent to output misleading error messages, like 'No line 6 in file
> "test.c".', when there actually is the line number 6, and the test case was
> compiled with "-g".
There must be more to the problem, since many people do this all the
time without any trouble. GDB has support for both cases. What
platform - is this Cygwin maybe? Is there any other test.c that GDB
might be opening?
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2007-03-12 20:49 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 [this message]
2007-03-12 21:06 ` Maxim Grigoriev
2007-03-12 21:23 ` Joel Brobecker
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=20070312204857.GA20515@caradoc.them.org \
--to=drow@false.org \
--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