From: Christopher Faylor <cgf@redhat.com>
To: gdb-patches@sources.redhat.com
Subject: Re: coffread.c extension for DLLs without debugging symbols
Date: Sun, 05 Jan 2003 17:18:00 -0000 [thread overview]
Message-ID: <20030105171826.GE16706@redhat.com> (raw)
In-Reply-To: <86k7hju04j.fsf@elgar.kettenis.dyndns.org>
On Sun, Jan 05, 2003 at 03:44:44PM +0100, Mark Kettenis wrote:
>Christopher Faylor <cgf@redhat.com> writes:
>
>>>>2) I wonder if this code should be ifdef'ed somehow for Windows since
>>>>it will add extra code for no gain on every COFF platform. Of course,
>>>>how many of those are there out there? Maybe this isn't a huge issue
>>>>after all.
>>>
>>>I wondered about that myself. However, wouldn't that suggest putting
>>>the bulk of the code somewhere like win32-nat.c?
>>
>> That would be fine with me (especially since I can approve that part of
>> gdb). So, you'd need some kind of hooks in coffread.c to handle this.
>> I guess we should wait for the coffread maintainer to offer an opinion
>> before you go to this effort, though.
>
>Well, I assume this code would be usefull when cross-debugging too.
>If so, a *-nat.c file would be the wrong place to add it. You could
>create a win32-tdep.c file though.
Cross debugging to a windows box? Does anyone actually do that? I know
it is theoretically possible with, *cough* rda *cough* but I wasn't aware
of anyone actually doing this.
Regardless, win32-tdep.c would be a more logically correct place to put
it.
cgf
next prev parent reply other threads:[~2003-01-05 17:18 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-03 19:41 Raoul Gough
2003-01-04 0:53 ` Michael Snyder
2003-01-04 4:43 ` Christopher Faylor
2003-01-04 16:31 ` Raoul Gough
2003-01-04 17:54 ` Eli Zaretskii
2003-01-04 20:51 ` Christopher Faylor
2003-01-05 14:44 ` Mark Kettenis
2003-01-05 17:18 ` Christopher Faylor [this message]
2003-01-05 17:40 ` Daniel Jacobowitz
2003-01-07 1:03 ` Raoul Gough
2003-01-07 1:12 ` Daniel Jacobowitz
2003-01-07 13:11 ` Raoul Gough
2003-01-07 16:46 ` Christopher Faylor
2003-01-07 2:28 ` Michael Snyder
2003-01-07 2:24 ` Michael Snyder
2003-01-04 11:03 ` Eli Zaretskii
2003-01-04 16:21 ` Raoul Gough
2003-01-06 17:10 ` Elena Zannoni
2003-01-06 17:41 ` Christopher Faylor
2003-01-07 0:46 ` Raoul Gough
2003-01-07 1:53 ` Elena Zannoni
2003-01-10 22:45 ` Raoul Gough
2003-01-07 1:00 ` Andrew Cagney
2003-01-10 22:37 ` Raoul Gough
2003-01-04 16:42 Michael Elizabeth Chastain
2003-01-05 15:40 ` Andrew Cagney
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=20030105171826.GE16706@redhat.com \
--to=cgf@redhat.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