Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Ulrich Weigand <uweigand@de.ibm.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [rfc] Remove current_gdbarch register handling from symbol readers
Date: Thu, 21 May 2009 03:27:00 -0000	[thread overview]
Message-ID: <8363fvp24e.fsf@gnu.org> (raw)
In-Reply-To: <200905210052.n4L0qMgq002959@d12av02.megacenter.de.ibm.com>

> Date: Thu, 21 May 2009 02:52:22 +0200 (CEST)
> From: "Ulrich Weigand" <uweigand@de.ibm.com>
> Cc: gdb-patches@sourceware.org
> 
> Only the Windows/DOS related targets remain.  Of those, all the
> -pe / -mingw / -cygwin / -interix targets actually use the PE
> file format, not "real" COFF, and GCC will default to generate
> stabs or DWARF-2 for those.  It seems possible to use -gcoff to
> force GCC to emit COFF/SDB debug info; I'm not sure if this will
> actually work with PE files ...

Well, I already tried that, and at least with MinGW GCC 3.4.2 that I
have installed, it fails: the binary produced with -gcoff is not
recognized by MinGW GDB 6.8 (it says "not in executable format").
Maybe it's a bug somewhere.

> The only target for which GCC by default generates COFF/SDB debug
> info does indeed appear to be -msdosdjgpp ...

DJGPP GCC uses DWARF-2 by default also, but it fully supports -gcoff.

The problem is that DJGPP does not support expect, so the the test
suite cannot be run.  I can run some tests manually, so if you or
someone else could tell which test may be affected by this change, I
can try running them.

Thanks.


  reply	other threads:[~2009-05-21  3:27 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-20 15:04 Ulrich Weigand
2009-05-20 17:42 ` Eli Zaretskii
2009-05-21  0:52   ` Ulrich Weigand
2009-05-21  3:27     ` Eli Zaretskii [this message]
2009-05-25 13:15       ` Ulrich Weigand
2009-05-25 20:59         ` Eli Zaretskii
2009-05-26 19:01           ` Ulrich Weigand
2009-06-04 12:36 ` Ulrich Weigand

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=8363fvp24e.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=uweigand@de.ibm.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