Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <dan@debian.org>
To: David Lecomber <david@streamline-computing.com>
Cc: patches <gdb-patches@sources.redhat.com>,
	Joel Brobecker <brobecker@gnat.com>
Subject: Re: [commit] Use full paths for "info sources"
Date: Tue, 21 Sep 2004 15:30:00 -0000	[thread overview]
Message-ID: <20040921153013.GA15014@nevyn.them.org> (raw)
In-Reply-To: <1095776238.14044.8.camel@elmo.priv.wark.uk.streamline-computing.com>

On Tue, Sep 21, 2004 at 03:17:18PM +0100, David Lecomber wrote:
> Alas this fix doesn't seem to fix it for me..

Thanks for checking.

> [david@delmo FOO]$ ls
> a.out  foo
> [david@delmo FOO]$ ~/bin/gdb a.out
> GNU gdb 20040920
> Copyright 2004 Free Software Foundation, Inc.
> GDB is free software, covered by the GNU General Public License, and you
> are
> welcome to change it and/or distribute copies of it under certain
> conditions.
> Type "show copying" to see the conditions.
> There is absolutely no warranty for GDB.  Type "show warranty" for
> details.
> This GDB was configured as "i686-pc-linux-gnu"...Using host libthread_db
> library "/lib/tls/libthread_db.so.1".
>                                                                                                                                                                    
> (gdb) info sources
> Source files for which symbols have been read
> in:                                                                                                                  
> Source files for which symbols will be read in on
> demand:                                                                                                                                                                   main.c, /home/david/FOO/foo/main.c
> (gdb)

This appears to be a problem in the pseudo-symtab code.  It needs to
take into account (A) the parent psymtab's dirname field and (B) the
directory table.  This is the decode_for_pst_p block in
dwarf_decode_lines.

I want to continue working on intercu support for now, but if Joel
doesn't have a chance to look at this, I will later.

-- 
Daniel Jacobowitz


  reply	other threads:[~2004-09-21 15:30 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-21 14:22 David Lecomber
2004-09-21 15:30 ` Daniel Jacobowitz [this message]
2004-09-24 21:16   ` Joel Brobecker
2004-10-13 23:12     ` David Lecomber
2004-10-13 23:24       ` Joel Brobecker
2004-10-14  0:08         ` David Lecomber
2004-10-16 23:56           ` Joel Brobecker
  -- strict thread matches above, loose matches on Subject: below --
2004-09-19 22:57 Daniel Jacobowitz

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=20040921153013.GA15014@nevyn.them.org \
    --to=dan@debian.org \
    --cc=brobecker@gnat.com \
    --cc=david@streamline-computing.com \
    --cc=gdb-patches@sources.redhat.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