Mail Archives: djgpp/2012/04/26/04:27:22
> From: Rugxulo <rugxulo AT gmail DOT com>
> Date: Thu, 26 Apr 2012 00:01:52 -0700 (PDT)
>
> > And I didn't (and don't) have time to work on fixing that.
> > But if someone gets that to work, I will happily switch, because COFF
> > debug info is barely supported in latest versions of GCC and GDB.
>
> I know this is a dumb question, but have you tried nagging the GCC or
> Cygwin people for help? Esp. for PE/COFF, what do they do for unexec?
The native Windows build of Emacs uses a separate file, unexw32.c.
Cygwin uses yet another file, unexcw.c.
> But you still (exclusively?) use an older GCC for your work anyways,
> right? 3.4.x?
Yes. "If it ain't broken, don't fix it."
> So I guess that will do for now.
"For now", yes. I'm under a lot of pressure from various Emacs
contributors to drop the DJGPP support. They question the size of the
user community that would like the DJGPP build to continue to exist.
With each new version of GCC, Binutils, GDB, or Make that move farther
away of supporting the DJGPP environment, I have less and less reasons
to continue fighting back. Expect me to give up some time soon.
> Sorry I can't help further, it's all Greek to me.
To me too, unfortunately. If someone who knows their way around
sections, debug info, and Binutils in general can have a look at
unexcoff.c and suggest what to do there to get a runnable, debuggable
emacs.exe after dumping, I'd be grateful.
- Raw text -