Date:	Sun, 28 Mar 1999 15:26:12 +0200 (IST)
From:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender:	eliz AT is
To:	BartMan <crazy-bartman AT geocities DOT com>
cc:	djgpp AT delorie DOT com
Subject:	Re: A problem with debugging under Rhide, more data
In-Reply-To:	<36FD6B64.58BE6645@geocities.com>
Message-ID:	<Pine.SUN.3.91.990328152552.22925l-100000@is>
MIME-Version:	1.0
Reply-To:	djgpp AT delorie DOT com
X-Mailing-List:	djgpp AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

On Sat, 27 Mar 1999, BartMan wrote:

> Call frame traceback EIPs:
>   0x0000b715   ___dj_movedata+33
>   0x00002b2b   _VM_GetBack__FiiUsUsPUs+135, line 239 of cr_pm.cc
>   0x00004367   _main+123, line 162 of cr_pm.cc
>   0x00004957   ___crt1_startup+115
> 
> D:\FLAKI\KOMP\GCC\WORK!\POINT>symify -o err p.exe
> 
> (this General Prot. Fault isn't important, because this is a bug in my
> program, but it shows place of an error)
> 
> !!!Hey! ->  0x00002b2b   _VM_GetBack__FiiUsUsPUs+135, line 239 of
> cr_pm.cc
> 
> A BUG! A procedure VM_GetBack() is in my video unit - cr_vm.cc file!
> Line number is correct, but file name is not correct.
> A cr_pm.cc file is main file, which is VM_GetBack() called from.

There's not enough info in your message to decide whether this is a
bug or not.  For example, if `VM_GetBack' is an inline function, then
the traceback is correct.  You need to disassemble the code to see how
GCC actually compiled that.

- Raw text -