Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Kris Warkentin <kewarken@qnx.com>
To: Daniel Jacobowitz <drow@false.org>
Cc: "Gdb-Patches@Sources.Redhat.Com" <gdb-patches@sources.redhat.com>
Subject: Re: [patch] Bring QNX Neutrino support forward.
Date: Thu, 01 Apr 2004 14:59:00 -0000	[thread overview]
Message-ID: <406C2EA6.2010501@qnx.com> (raw)
In-Reply-To: <20040331222120.GB6811@nevyn.them.org>

I've been looking at the *nto-tdep files and it looks like I've got some 
refactoring to do in order to be current.  Particularily the 
supply_regset stuff and the whole core_fns deprecation thing.  Looks 
icky and I'm not really sure of the best way to do it.  I've got 4 other 
targets besides i386 so I'm looking for the most efficient way.  I'm 
thinking that I might be able to take advantage of more of the generic 
stuff in i386-tdep.c, at least for that target.

Daniel Jacobowitz wrote:

>Leading tabs in the ChangeLog entry, please :)  Post what you would
>check in.
>  
>

Lost in translation.  They're there in real life. ;-)

>>-  return openp (buf, 1, solib, o_flags, 0, temp_pathname);
>>+  /* Don't assume basename() isn't destructive.  */
>>+  base = strrchr (solib, '/');
>>+  if (!base)
>>+    base = solib;
>>+  else
>>+    base++;			/* Skip over '/'.  */
>>    
>>
>
>There's an lbasename in libiberty, for this reason.  You should use
>that instead.
>
>  
>
Cool.  I did not know that.

>>+  ret = openp (buf, 1, base, o_flags, 0, temp_pathname);
>>+  if (ret < 0 && base != solib)
>>+    {
>>+      sprintf (arch_path, "/%s", solib);
>>+      ret = open (arch_path, o_flags, 0);
>>    
>>
>
>Er... automatically falling back to the host library?  Why?
>  
>

I'm looking through solib_open() and trying to recreate my reasoning.  
It certainly seemed like a good idea at the time.  Let's say the linker 
has the library as /home/kewarken/libfoo.so.  Given the current 
solib_open, I don't believe that gdb will find it without having 
solib-search-path set.  I put that there as a 'just in case' thing 
because a) it works well on self hosted and b) even for remote 
debugging, we often match the host and target filesystems.  I figured 
that all common libs like libc.so, etc. would have been caught by the 
openp() above so the odds of accidentally getting a host library are 
slim.  This makes things a bit easier for the user: the linker fills in 
the full path and gdb uses it rather than requiring a solib-search-path.

cheers,

Kris


  reply	other threads:[~2004-04-01 14:59 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-23 21:18 Kris Warkentin
2004-03-23 23:21 ` Andrew Cagney
2004-03-24 13:38   ` Kris Warkentin
2004-03-24 14:35     ` Andrew Cagney
2004-03-24 16:32       ` Kris Warkentin
2004-03-25 17:22         ` Kris Warkentin
2004-03-26  3:43           ` Andrew Cagney
2004-03-31 22:21 ` Daniel Jacobowitz
2004-04-01 14:59   ` Kris Warkentin [this message]
2004-04-01 15:04     ` 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=406C2EA6.2010501@qnx.com \
    --to=kewarken@qnx.com \
    --cc=drow@false.org \
    --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