From: Daniel Jacobowitz <drow@false.org>
To: Steve Kreyer <steve.kreyer@web.de>
Cc: gdb@sourceware.org
Subject: Re: Using dlopen and remote debugging
Date: Wed, 27 Feb 2008 01:23:00 -0000 [thread overview]
Message-ID: <20080227010622.GA26188@caradoc.them.org> (raw)
In-Reply-To: <1016245125@web.de>
On Mon, Feb 25, 2008 at 05:29:33PM +0100, Steve Kreyer wrote:
> Unfortunately your response did not receive my email service
> provider til now. I had to read it over the gdb mailing list
> archives. Thank you so much for this patch you've suggested there!
> I've searched nearly 2 days for a solution about this issue, now it
> works!
Thanks for testing. I've checked it in.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2008-02-27 1:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-25 19:29 Steve Kreyer
2008-02-27 1:23 ` Daniel Jacobowitz [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-02-25 14:33 steve.kreyer
2008-02-25 16:33 ` Daniel Jacobowitz
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
2008-02-25 13:32 ` 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=20080227010622.GA26188@caradoc.them.org \
--to=drow@false.org \
--cc=gdb@sourceware.org \
--cc=steve.kreyer@web.de \
/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