Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <pedro@codesourcery.com>
To: danny.backx@scarlet.be
Cc: gdb-patches@sourceware.org
Subject: Re: How to fix solib path name?
Date: Wed, 08 Jul 2009 16:19:00 -0000	[thread overview]
Message-ID: <200907081657.38489.pedro@codesourcery.com> (raw)
In-Reply-To: <1247067931.3870.76.camel@pavilion>

On Wednesday 08 July 2009 16:45:31, Danny Backx wrote:
> On Wed, 2009-07-08 at 17:31 +0200, Danny Backx wrote:
> > On Wed, 2009-07-08 at 16:07 +0100, Pedro Alves wrote:
> > > Maybe we can make gdbserver smarter even on CE < 6?  I think I
> > > remember that if you had toolhelp.dll on the device, you'd get
> > > absolute paths, but I'm not sure if that's a valid memory I have.
> > > 
> > 
> > I've added one printf statement to gdbserver/server.c just after where
> > it assembles the library name list.
> > 
> > Output on the infamous C++ hello2.exe below. Two out of the three are
> > absolute path names. Not sure why the other one isn't.
> > 
> > Is it best to adapt gdbserver for this ?
> 
> If the answer to my question is yes, then it's not a hard fix. It's
> attached.

No, that's the wrong direction.  Absolute paths are better.  I'd
rather we make a better effort at finding the pathname in the cases we
don't know them.

Losing information like this is never good.  At most, we could add a
knob to gdb to ignore the path information and look at the filename
only.

But, please, let's not go around and around, when I suggested "set sysroot"
several times already.  Did you actually try that?  Please do,
before posting more patches.

-- 
Pedro Alves


  reply	other threads:[~2009-07-08 15:57 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-08 14:34 Danny Backx
2009-07-08 14:45 ` Aleksandar Ristovski
2009-07-08 14:51   ` Pedro Alves
2009-07-08 15:15     ` Aleksandar Ristovski
2009-07-08 15:21       ` Pedro Alves
2009-07-08 15:38         ` Aleksandar Ristovski
2009-07-08 15:49           ` Pedro Alves
2009-07-08 15:57             ` Pedro Alves
2009-07-08 17:19             ` Aleksandar Ristovski
2009-07-08 18:24               ` Pedro Alves
2009-07-08 18:30                 ` Pedro Alves
2009-07-08 14:56 ` Pedro Alves
2009-07-08 15:07   ` Pedro Alves
2009-07-08 15:31     ` Danny Backx
2009-07-08 15:45       ` Pedro Alves
2009-07-08 15:45       ` Danny Backx
2009-07-08 16:19         ` Pedro Alves [this message]
2009-07-08 16:30           ` Danny Backx
2009-07-08 16:42             ` Pedro Alves
2009-07-08 17:15   ` Pedro Alves
2009-07-08 20:46     ` Danny Backx

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=200907081657.38489.pedro@codesourcery.com \
    --to=pedro@codesourcery.com \
    --cc=danny.backx@scarlet.be \
    --cc=gdb-patches@sourceware.org \
    /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