From: "Pedro Alves" <pedro_alves@portugalmail.pt>
To: gdb@sourceware.org
Subject: Re: Win32 gdbserver dll support.
Date: Thu, 03 May 2007 16:11:00 -0000 [thread overview]
Message-ID: <4053daab0705030911v4be55c85jcce7d0fb2d24dde0@mail.gmail.com> (raw)
In-Reply-To: <20070503153703.GA20130@caradoc.them.org>
Hi Daniel,
On 5/3/07, Daniel Jacobowitz <drow@false.org> wrote:
> On Sun, Apr 29, 2007 at 10:45:31PM -0400, Daniel Jacobowitz wrote:
> > > I'll take a deeper look at the patch in a couple of days.
> >
> > Thanks. So will I. Maybe I can simplify it further.
>
> FYI, I'm still working on this. I've got all of my existing code to
> work with trunk at last.
>
Glad you're working on this, and was going to report tonight :)
I looked into it last night too. I've got cygwin native working with
your solib-target.c, to get a feeling if it would be a good match. It is.
There is just one case, that I bet you'll be looking into, which is
the relocate_section_addresses solib-target op. Your implementation
was elf specific. To get it up working as a fast prototype, I used
a method that wouldn't work for elf.
I stumbled on core dump support, dll loading. Current win32-nat.c
reads the dlls
that were loaded in the core, on win32_current_sos, depending on core_bfd
being set. Perhaps we need a new op somewhere, maybe in struct core_fns too.
Anyway, I'm writing this on a hurry.
Perhaps you would want to take a look at my changes, to get a better feeling
of what is needed for win32. I'll get home in a few hours.
Cheers,
Pedro Alves
next prev parent reply other threads:[~2007-05-03 16:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-26 16:41 Pedro Alves
2007-04-26 22:27 ` Pedro Alves
2007-04-26 22:44 ` Daniel Jacobowitz
2007-04-26 23:34 ` Pedro Alves
2007-04-30 2:45 ` Daniel Jacobowitz
2007-05-03 15:37 ` Daniel Jacobowitz
2007-05-03 16:11 ` Pedro Alves [this message]
2007-05-03 20:08 ` Daniel Jacobowitz
2007-05-03 21:44 ` Pedro Alves
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=4053daab0705030911v4be55c85jcce7d0fb2d24dde0@mail.gmail.com \
--to=pedro_alves@portugalmail.pt \
--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