From: "Dr. Rolf Jansen" <rj@surtec.com>
To: gdb@sourceware.org
Subject: Re: Using dlopen and remote debugging
Date: Mon, 25 Feb 2008 14:23:00 -0000 [thread overview]
Message-ID: <4DD16CA6-AF98-4599-A9F5-CAF0EA4F3E84@surtec.com> (raw)
In-Reply-To: <20080225133150.GB19361@caradoc.them.org>
Am 25.02.2008 um 10:31 schrieb Daniel Jacobowitz:
> On Mon, Feb 25, 2008 at 10:03:09AM -0300, Dr. Rolf Jansen wrote:
>
>> In my case this was impossible. The remote machine happened to run
>> Windows XP and the host Mac OS X. I found no way to let Mac OS X
>> understand a full path like "C:\path\to\my\exe\and\dll. I needed to
>> patch
>> gdbserver. In the latest CVS version I changed server.c beginning
>> at line
>> 528 to:
>
> Then just set solib-search-path; GDB will look up the basenames.
I did this to no avail.
> There is an additional wrinkle involving path separators, since GDB
> is likely to think that is bare filename and not a full path.
Yeah, as I said, the host gdb at the Mac does not understand the path
semantics that is send from gdbserver at Windows.
> But it should be fixed on the GDB side, not on the target side.
I am comfortable with that - fix it however and whenever you want!
Once it is fixed, I will abandon my quick hack. Until that I have a
working solution.
> This one's been discussed a few times recently.
Discussions are good, solutions are better - even quick 'n dirty ones.
Rolf
next prev parent reply other threads:[~2008-02-25 13:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-25 12:15 Steve Kreyer
2008-02-25 13:30 ` Dr. Rolf Jansen
2008-02-25 13:55 ` Daniel Jacobowitz
2008-02-25 14:23 ` Dr. Rolf Jansen [this message]
2008-02-25 13:32 ` Daniel Jacobowitz
2008-02-25 14:33 steve.kreyer
2008-02-25 16:33 ` Daniel Jacobowitz
2008-02-25 19:29 Steve Kreyer
2008-02-27 1:23 ` 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=4DD16CA6-AF98-4599-A9F5-CAF0EA4F3E84@surtec.com \
--to=rj@surtec.com \
--cc=gdb@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