Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Christopher Faylor <cgf@redhat.com>
To: gdb-patches@sources.redhat.com
Cc: RaoulGough@yahoo.co.uk
Subject: Re: coffread.c extension for DLLs without debugging symbols
Date: Sat, 04 Jan 2003 04:43:00 -0000	[thread overview]
Message-ID: <20030104044408.GA7364@redhat.com> (raw)
In-Reply-To: <av4os0$f0q$1@main.gmane.org>

On Fri, Jan 03, 2003 at 07:39:31PM -0000, Raoul Gough wrote:
>Proposed ChangeLog entry, assuming the code is accepted:
>
>2003-01-03  Raoul Gough  <RaoulGough@yahoo.co.uk>
>
> * coffread.c: Support non-debug export symbols for win32 DLLs

WONDERFUL! I would love to have this code in the windows version of gdb.
I've often thought about doing something like this but I've never had
the stamina to look into what it would take to do this.

I have a few comments.

0) The ChangeLog needs more information.  Every new function should be
mentioned and changes to specific functions should be documented.

1) AFAICT, the formatting of the code looks great (a rarity for a first
timer) except for an odd comment or two which doesn't end in a "." as
required for a complete sentence.  Yeah, yeah, a total nit but hey we've
got standards!

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.

3) objdump -p already has the ability to read and report on the export
table.  I wonder if it would be useful (or possible) to generalize this
code so that gdb and objdump would be using the same base.  I haven't
looked too closely but I think the code in question is in bfd/peicode.h.
Hmm.  Maybe objdump isn't interested in the kinds of things that gdb
is, though, like what section a symbol is associated with...

Anyway, I'll be giving this an actual test run in the next couple of
days.  In the meantime, THANK YOU for doing this.  Even given the very
minor above points, I think this will be a great boon for the Windows
version of gdb.  This will help enormously in debugging on Windows.

You will definitely need to get an assignment in to the FSF, though,
unfortunately.  I think jimb at redhat dot com is the person to help
you with that.

cgf

P.S.  Assuming that this works as advertised, I assume that you will
have no objections to my releasing a new version of gdb for windows
with this patch in it before the patch makes its way into the official
gdb repository, right?  I think there are a few users in the cygwin
mailing list that would appreciate this change.
--
Special for spam email harvesters: send email to aaaspam@sources.redhat.com
and be permanently blocked from mailing lists at sources.redhat.com.


  parent reply	other threads:[~2003-01-04  4:43 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 [this message]
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
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=20030104044408.GA7364@redhat.com \
    --to=cgf@redhat.com \
    --cc=RaoulGough@yahoo.co.uk \
    --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