Date: Wed, 28 Jul 1999 10:33:15 +0300 (IDT) From: Eli Zaretskii X-Sender: eliz AT is To: Richard Dawe cc: DJGPP newsgroup Subject: Re: Bizarre debugging format problem In-Reply-To: <379CE004.2ED68B91@tudor21.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Reply-To: djgpp AT delorie DOT com X-Mailing-List: djgpp AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk On Mon, 26 Jul 1999, Richard Dawe wrote: > The 2.02 version gives line numbers on running symify: When you ran symify on v2.02-compiled program, was symify.exe itself from v2.02 or from v2.01? v2.02 corrects a subtle bug in libdbg.a functions that read debug info from the executable (the old version would crash FSDB is some cases), so it's possible that the new symify is also better in this aspect). > Hello mum! > Hello world! > Exiting due to signal SIGINT > Control-Break Pressed at eip=0000706e > eax=00000000 ebx=00000021 ecx=00000000 edx=0000000d esi=00000044 > edi=0004e86c > ebp=0004e85c esp=0004e850 program=D:\DEVELOP\TEST\dbginfo\testit2 > cs: sel=013f base=83501000 limit=0005ffff > ds: sel=0147 base=83501000 limit=0005ffff > es: sel=010f base=83501000 limit=0005ffff > fs: sel=0137 base=000161f0 limit=00003fff > gs: sel=014f base=00000000 limit=ffffffff > ss: sel=0147 base=83501000 limit=0005ffff This doesn't seem like a v2.02 traceback. Did I miss something?