This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [rfc] Remove current_gdbarch register handling from symbol readers
- From: Eli Zaretskii <eliz at gnu dot org>
- To: Ulrich Weigand <uweigand at de dot ibm dot com>
- Cc: gdb-patches at sourceware dot org
- Date: Mon, 25 May 2009 23:59:11 +0300
- Subject: Re: [rfc] Remove current_gdbarch register handling from symbol readers
- References: <200905251314.n4PDEdWQ015511@d12av02.megacenter.de.ibm.com>
- Reply-to: Eli Zaretskii <eliz at gnu dot org>
> 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.