From:	Laurent DOT CHARLES AT st DOT com
Date:	Fri, 13 Dec 96 14:31:47 +0100
Message-Id:	<H000030d03e26d0f@MHS>
Subject:	Debugging cross compiled programs.
Mime-Version:	1.0
Sender:	Laurent DOT CHARLES AT st DOT com
To:	djgpp AT delorie DOT com

Hi all,

Here are some problems we have when using gdb.

Context:
We are building a cross compiler from gcc-2.7.2 to an embedded micro-controler.
One goal is to have the toolset working on sunos, msdos, windows3.1, windows95,
Windows NT...!

We chose to have a unified build process working on sunos with cross-compiler to
the microsoft targets. That's why we used a cross gcc to go32/dpmi.

Problems occur when we want to debug on our targetted host (msdos).

1) To do that we use djgpp-gdb (v4.16) working on an distant NFS volume.
Our workstations are WinNT4.0 machines, running dos boxes when necessary. 
We can switch to real dos/windows.
Do you think this is a viable way to work?

We also think of doing remote debugging, but we don't know how, not even if it's
possible. Has anyone of you ever succedded in doing that.

Is there another way to debug? Another debugger (other than fsdb)?

2) The source file names are original file names (long). And of course the file
names that the msdos box provides are not the same (8.3). We tried to use
WindowsNT dos box, but gdb sees the dos names (I guess because it accesses files
through dos), therefore can't debug at the source level.
Did anyone ever have such problem? How to solve that?
Is there a way to tell gdb to use source file names other than the orginal ones
(command such as 'mapfile long-file-name.c dosname.c' - We're thinking of adding
it to gdb)?

3) How to catch signals from gdb? Especially floating point exceptions.

Thankx for your help.


--Laurent

- Raw text -