Sender: richdawe AT bigfoot DOT com
Message-ID: <379CE004.2ED68B91@tudor21.net>
Date: Mon, 26 Jul 1999 23:24:04 +0100
From: Richard Dawe <richdawe AT bigfoot DOT com>
X-Mailer: Mozilla 4.51 [en] (X11; I; Linux 2.2.10 i586)
X-Accept-Language: de,fr
MIME-Version: 1.0
To: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
CC: DJGPP newsgroup <djgpp AT delorie DOT com>
Subject: Re: Bizarre debugging format problem
References: <Pine DOT SUN DOT 3 DOT 91 DOT 990725110455 DOT 27488E-100000 AT is>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Reply-To: djgpp AT delorie DOT com

Hello.

Eli Zaretskii wrote:
> This seems to indicate that there's a real problem with line-number
> info in this program: symify didn't print them as well.  Could you
> please make this binary available for downloading, or send it to me?
> I want to look into it some more.

I have uploaded the Makefile, C source and binaries compiled with DJGPP
2.01 & 2.02 + gcc 2.8.1 here:

http://www.phekda.freeserve.co.uk/richdawe/djgpp/

> This traceback also shows that you still use v2.01 library.  Why?

Partially habit, but also because I was trying to finish a new version of
libsocket before switching to 2.02. Maybe I will give up on this and just
switch to 2.02, given the time it's taking for the new release ;) However,
I do have 2.02 on my computer, and I've rerun the '-g' & '-gstabs' tests
with it (see below).

> > BTW is the result of running symify a symification?
> 
> You mean, as opposed to symifization?

I guess so ;)

> I can make the gdb.exe binary available for anon ftp, if you want.

That would be good, if it's not too much trouble.

> As for the test program, it seems that the modified program, without
> libsocket, also exhibits the problem, and it is probably much
> smaller.  So perhaps you could send it to me.

If the above address doesn't work, I can e-mail you the files.

> Btw, how did you compile the program (with what switches)?

I compiled the DJGPP 2.01 + gcc 2.8.1 version using:

gcc -gstabs -Wall -Id:/develop/lsck/include -c testit2.c
gcc -gstabs -Ld:/develop/lsck/lib -o testit2 testit2.o

I firstly compiled the DJGPP 2.02 + gcc 2.8.1 version using:

gcc -g -Wall -Id:/develop/lsck/include -c testit2.c
gcc -g -Ld:/develop/lsck/lib -o testit2 testit2.o

NB: The libsocket includes & libs are not needed for testit2, but were for
testit.

The 2.02 version gives line numbers on running symify:

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

Call frame traceback EIPs:
  0x0000706e   ___dpmi_int+114
  0x00002545   _getch+49
  0x000015e9   _main+37, line 11 of testit2.c
  0x00001b56   ___crt1_startup+138
bash$ symify testit2.exe

'-g' was not enough to allow me to use 'l main' in gdb - the original
problem. Using '-gstabs' fixed this. I secondly compiled the 2.02 binary
available from my web page using these switches:

gcc -g -Wall -Id:/develop/lsck/include -c testit2.c
gcc -g -Ld:/develop/lsck/lib -o testit2 testit2.o

I hope this is enlightening in some way. Bye,

-- 
--------------+----------------------+------------------------------------
 Richard Dawe | richdawe AT bigfoot DOT com | http://www.bigfoot.com/~richdawe/ 
--------------+----------------------+------------------------------------