Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: Elena Zannoni <ezannoni@redhat.com>
Cc: Alexander Larsson <alexl@redhat.com>,
	gdb@sources.redhat.com, Jim Blandy <jimb@redhat.com>
Subject: Re: External debug symbols
Date: Fri, 20 Sep 2002 08:22:00 -0000	[thread overview]
Message-ID: <20020920152236.GA9109@nevyn.them.org> (raw)
In-Reply-To: <15755.14989.816244.777522@localhost.redhat.com>

On Fri, Sep 20, 2002 at 11:11:09AM -0400, Elena Zannoni wrote:
> 
> I have looked at this. I think it's a valuable thing to have.  I have
> a few questions about the approach, and a few more specific comments
> about the code. I haven't followed all the implications of this patch.
> What do other folks think?

In general, I'm in love with it.

>  > diff --exclude '*~' --exclude '*.orig' --exclude '*.rej' --exclude '.#*' --exclude '*.o' --exclude CVS --exclude SCCS --exclude RCS --exclude '.*.flags' --exclude .cvsignore --exclude .depend -ur gdb-5.2.1/gdb/configure.in gdb-5.2.1.separate_debug_symbols/gdb/configure.in
>  > --- gdb-5.2.1/gdb/configure.in	Thu Mar 28 05:28:00 2002
>  > +++ gdb-5.2.1.separate_debug_symbols/gdb/configure.in	Mon Aug 26 17:02:48 2002
>  > @@ -234,6 +234,14 @@
>  >  AC_CHECK_LIB(socket, socketpair)
>  >  AC_CHECK_FUNCS(socketpair)
>  >  
>  > +debugdir=${libdir}/debug
>  > +	 
>  > +AC_ARG_WITH(separate-debug-dir,
>  > +[  --with-separate-debug-dir=path   Look for global separate debug info in this path [LIBDIR/debug]],
>  > +[debugdir="${withval}"])
>  > +	
>  > +AC_DEFINE_DIR(DEBUGDIR, debugdir)
>  > +#AC_DEFINE_UNQUOTED(DEBUGDIR, "$debugdir"),
>  >  
> 
> Could this be done alternatively using an environment variable,
> instead of being set at configure time? something like
> DEBUG_INFO_PATH, or similar.  I don't have a strong preference, but
> seems to me that an environment variable is more flexible. 

I'd have to change this for local GDB packages anyway.  Full
relocatable installs are a must for me, so I'd have to make this path
follow the current location of the GDB binary.  I'm hoping to put the
necessary support code in libiberty eventually...
 
> Thinking out loud...
> 
> I wonder if it wouldn't be more intuitive to add the debug info to the
> objfile, instead of creating another objfile.  So that in the end we
> would have just a new field added to the objfile, indicating the name
> of the debug info file.

I like this idea; it seems a lot less fragile.


-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer


  reply	other threads:[~2002-09-20 15:22 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-20 12:50 Alexander Larsson
2002-08-21  6:39 ` Alexander Larsson
2002-08-21 10:46 ` Jim Blandy
2002-08-21 23:51   ` Alexander Larsson
2002-08-27  3:59   ` Alexander Larsson
2002-09-16  6:59     ` Alexander Larsson
2002-09-20  8:13       ` Elena Zannoni
2002-09-20  8:22         ` Daniel Jacobowitz [this message]
2002-09-23  0:46           ` Alexander Larsson
2002-09-23  0:43         ` Alexander Larsson
2002-09-23  8:21         ` Alexander Larsson
2002-09-23  8:25           ` Daniel Jacobowitz
2002-09-23 10:03             ` Alexander Larsson
2002-09-23 21:45           ` Eli Zaretskii
2002-09-25  1:51             ` Alexander Larsson
2002-09-25 22:00               ` Eli Zaretskii
2002-10-02  7:42                 ` Alexander Larsson
2002-10-02 21:40                   ` Eli Zaretskii
2002-10-08  8:21                     ` Alexander Larsson
2002-10-08  9:33                       ` Eli Zaretskii

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=20020920152236.GA9109@nevyn.them.org \
    --to=drow@mvista.com \
    --cc=alexl@redhat.com \
    --cc=ezannoni@redhat.com \
    --cc=gdb@sources.redhat.com \
    --cc=jimb@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