Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Eli Zaretskii" <eliz@is.elta.co.il>
To: RaoulGough@yahoo.co.uk
Cc: gdb-patches@sources.redhat.com
Subject: Re: coffread.c extension for DLLs without debugging symbols
Date: Sat, 04 Jan 2003 17:54:00 -0000	[thread overview]
Message-ID: <6480-Sat04Jan2003195141+0200-eliz@is.elta.co.il> (raw)
In-Reply-To: <av71qf$glr$1@main.gmane.org> (RaoulGough@yahoo.co.uk)

> From: "Raoul Gough" <RaoulGough@yahoo.co.uk>
> Date: Sat, 4 Jan 2003 16:25:16 -0000
> 
> How's this:
> 
> 2003-01-03  Raoul Gough  <RaoulGough@yahoo.co.uk>
> 
>  * coffread.c: Support non-debug export symbols for win32 DLLs.
>  (coff_symtab_read): call read_pe_exported_syms iff no symbols
>  found and objfile is "pe-i386" or "pei-i386".
>  (read_pe_exported_syms): New function.
>  (read_pe_section_data): New struct (temporary section info).
>  (read_pe_section_index): New function.
>  (read_pe_truncate_name): New function.
>  (get_section_vmas): New function.
>  (add_pe_exported_sym): New function.
>  (pe_get16, pe_get32, pe_as32): New functions.

This is okay, thanks.

> > 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?

The DJGPP port of GDB uses COFF (and doesn't support DLLs).


  reply	other threads:[~2003-01-04 17:54 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 [this message]
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=6480-Sat04Jan2003195141+0200-eliz@is.elta.co.il \
    --to=eliz@is.elta.co.il \
    --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