Mail Archives: djgpp-workers/1999/03/25/13:57:42
> If you think this will be safe, I don't have any objections. It would
> be nice, though, if somebody would build GDB 4.16 with the modified
> dbgcom.c and make sure it works.
This will be probably need some changes to the gdb sources
(or at least a complete reconfiguring of the preconfigured sources).
As I last tried to rebuild gdb 4.16 with DJGPP 2.02 I failed but
I really had not the motivation to try it deeper since there is gdb 4.17
already available for a long time and I'm waiting for 4.18
I think also, if Andris says, that it is enough tested and the exception
stuff should be applied but that's only my personal opinion, since
I don't understand that new changes to say if it is safe or not.
But as I said already in the past, that changes should be made more
clear. In my opinion the
#ifdef FPC
and so on should be removed since they don't belong to DJGPP and
also the cvs keywords.
And a last note, not really to this topic: Maybe sometimes someone
will clean up all (or most) of the assembler code to C code and have
only the really necessary code in assembler because I think, that
most of us can read a C fragment much better than assembler and
for a debugger there is no need to think about speed.
******************************************************
* email: Robert Hoehne <robert DOT hoehne AT gmx DOT net> *
* Post: Am Berg 3, D-09573 Dittmannsdorf, Germany *
* WWW: http://www.tu-chemnitz.de/~sho/rho *
******************************************************
- Raw text -