This is the mail archive of the gdb-patches@sources.redhat.com mailing list for the GDB project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: [commit] Use full paths for "info sources"

From: Joel Brobecker <brobecker at gnat dot com>
To: David Lecomber <david at streamline-computing dot com>
Cc: dan at debian dot org, patches <gdb-patches at sources dot redhat dot com>
Date: Sat, 16 Oct 2004 16:56:03 -0700
Subject: Re: [commit] Use full paths for "info sources"
References: <1095776238.14044.8.camel@elmo.priv.wark.uk.streamline-computing.com> <20040921153013.GA15014@nevyn.them.org> <20040924211628.GC11798@gnat.com> <1097605852.9994.3.camel@localhost.localdomain> <20041013232403.GU1375@gnat.com> <1097712892.11117.75.camel@localhost.localdomain>

> > I haven't reviewed the entire thread yet. Was this something really
> > bad. Or is it just duplication we get in the output, and that's it?
> 
> One problem is that things appear in the info sources, and info source,
> and in the stack traces, with different paths.  So once you've got your
> definitive path for a file, you then see it referred to in a different
> way when you start using it.  Work-roundable for the user I guess, but
> less than ideal.

I just had a look. I think I have a fix for it, but I might just have
opened a can of worms... In any case, I'm working on it.

-- 
Joel

References:
- Re: [commit] Use full paths for "info sources"
  - From: David Lecomber
- Re: [commit] Use full paths for "info sources"
  - From: Joel Brobecker
- Re: [commit] Use full paths for "info sources"
  - From: David Lecomber

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]