Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Aleksandar Ristovski <aristovski@qnx.com>
To: gdb-patches@sources.redhat.com
Subject: Re: How to fix solib path name?
Date: Wed, 08 Jul 2009 14:45:00 -0000	[thread overview]
Message-ID: <h32be7$k86$1@ger.gmane.org> (raw)
In-Reply-To: <1247063678.3870.59.camel@pavilion>

Danny Backx wrote:
> I'm preparing a gdb patch so it works in a cross-debugging environment.
> Host I'm using is a linux pc, target is running Windows CE Embedded 6.0.
> 
> The gdbserver part is getting complete, see other messages on this list.
> 
> The gdb still has a quirck or two.
> 
> (gdb) info sharedlibrary
>>From        To          Syms Read   Shared Object Library
>                         No          \network\x86\libgcc_s_sjlj-1.dll
> 0x41ee1000  0x41fb2974
> Yes         /opt/x86mingw32ce/i386-mingw32ce/lib/libstdc++-6.dll
>                         No          \Windows\coredll.dll
> (gdb) 
> 
> I'm guessing that it should strip the \network\x86 from the library name
> before it attempts to find it in the solib-search-path.

See solib_find comment in "solib.c" for figuring out how it 
looks for it.

You can provide "find_and_open_solib" in your target_ops for 
customizing it (in case you want to provide "default" search 
algorithm when built-in solib-search-path mechanism fails to 
find it).

> 
> Should it ?
> 
> If yes, where should the code for that be ?
> 
> Thanks for the help. Once this gets fixed, I can submit that part of my
> work too.
> 
> 	Danny


-- 
Aleksandar Ristovski
QNX Software Systems


  reply	other threads:[~2009-07-08 14:45 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 [this message]
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       ` Danny Backx
2009-07-08 16:19         ` Pedro Alves
2009-07-08 16:30           ` Danny Backx
2009-07-08 16:42             ` Pedro Alves
2009-07-08 15:45       ` 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='h32be7$k86$1@ger.gmane.org' \
    --to=aristovski@qnx.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