Re: Alexei fixes for NASM w/Borland TD

On Aug 22, 1:23 am, "Rod Pemberton" <do_not_h...@xxxxxxxxxxxxx> wrote:
"Alexei A. Frounze" <alexfrun...@xxxxxxxxx> wrote in messagenews:2d7b1027-9f13-4602-b810-b9b0813070c2@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx



I was only involved in two things, which I thought were bad ('cause I
needed them to work:):
1. include paths for INCBIN and the direction of the path traversal.
I've been credited for this somewhere in the doc.
2. broken symbolic debug information for Turbo Debugger. I don't
remember if this actually got fixed or reverted to what it was. The
problem AFAIR was that some of the state was saved in variables
declared as static and some NASM's functions were relying on those to
keep the state between the calls. Somebody very smartly decided to
"fix" these ugly static variables and just dropped static effectively
turning the variables into local ones. The wrong fix broke the
symbolic info.
I sent a bunch of messages on this to nasm-devel at lists... and
exchanged some info with Frank. The messages were from July 2003 and
their subject line contained:
a) Nasm + Borland ( was Once more time - outbin.c (fwd))
b) NASM's Borland Debug Info Output
I think I wasn't credited for this and that's because probably it
didn't get fixed...
Can somebody look this up in the old mail

http://sourceforge.net/mailarchive/message.php?msg_name=002e01c348ce%...http://sourceforge.net/mailarchive/message.php?msg_name=010001c34715%...http://sourceforge.net/mailarchive/forum.php?thread_name=000a01c348d4...


Yep those. I still have the e-mails from those threads and all
attachments. So, if somebody wants to fix a real bug or confirm it
already being fixed, I may share those if needed.

and then in the NASM source?

I'll leave that to someone more familiar...

Same here. I just kept using the old NASM without that bug.

Alex
.

Relevant Pages