Date: Tue, 31 Jul 2001 11:41:43 +0300 (IDT)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: jansb000 <jansb000 AT wxs DOT nl>
cc: djgpp AT delorie DOT com
Subject: Re: Question about symify
In-Reply-To: <9k4hp7$1v6tu$1@reader03.wxs.nl>
Message-ID: <Pine.SUN.3.91.1010731114125.1042G-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


On Mon, 30 Jul 2001, jansb000 wrote:

> Q: Why is symify not able to give me all the line-numbers? (it shows double
> questionmarks instead).

The answer to that is in the sources of maptfile.cpp and mapview.cpp,
which you didn't show.  For example, if the code for the crashed
functions comes from some #include'd header file, the COFF debug info
lists wrong line numbers there.

GDB might be of more help here, especially if you compile the program
with -gstabs+ switch instead of -g.  Section 9.3 of the FAQ tells how
to display a source line given the value of EIP where the program
crashed.

Btw, in your case, the first place to look would be the bad selector
loaded into FS:

> fs: sel=00d7  invalid

Did you use some function such as _farpeekb in some wrong way?