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: Mon, 25 May 2009 20:59:00 -0000	[thread overview]
Message-ID: <83skissxuo.fsf@gnu.org> (raw)
In-Reply-To: <200905251314.n4PDEdWQ015511@d12av02.megacenter.de.ibm.com>

> Date: Mon, 25 May 2009 15:14:39 +0200 (CEST)
> From: "Ulrich Weigand" <uweigand@de.ibm.com>
> Cc: gdb-patches@sourceware.org
> 
> So overall it seems that *no* target uses COFF/SDB debug info as its
> default format any more; those that still support it at all also use
> a more powerful format as default.  Under those circumstances, is there
> any benefit to continuing to support that format in GDB, given that it
> becomes more and more diffcult to test that this support actually
> still works?

DJGPP needs support for the COFF debug info because the DJGPP port of
Emacs can only be built with -gcoff.  That's because no one ported
unexec.c in Emacs to DWARF-2 debug info embedded in COFF binary
format.  I don't expect such changes in unexec.c any time soon.

> > 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.
> 
> Pretty much any access to an in-register local variable or parameter
> should break if the change is wrong.

OK, I will run at least some of them.


  reply	other threads:[~2009-05-25 20:59 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
2009-05-25 13:15       ` Ulrich Weigand
2009-05-25 20:59         ` Eli Zaretskii [this message]
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=83skissxuo.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