www.digitalmars.com Home | Search | C & C++ | D | DMDScript | News Groups | index | prev | next
Archives

D Programming
D
D.gnu
digitalmars.D
digitalmars.D.bugs
digitalmars.D.dtl
digitalmars.D.dwt
digitalmars.D.announce
digitalmars.D.learn
digitalmars.D.debugger

C/C++ Programming
c++
c++.announce
c++.atl
c++.beta
c++.chat
c++.command-line
c++.dos
c++.dos.16-bits
c++.dos.32-bits
c++.idde
c++.mfc
c++.rtl
c++.stl
c++.stl.hp
c++.stl.port
c++.stl.sgi
c++.stlsoft
c++.windows
c++.windows.16-bits
c++.windows.32-bits
c++.wxwindows

digitalmars.empire
digitalmars.DMDScript

c++ - strange debugger behaviour

↑ ↓ ← rehjr optusnet.com.au writes:
I received my Digital Mars CD a few days ago,
and have been beating my head against the wall
trying to make it work.  It runs all right, and
even compiles minimal programs.  But when I try
to compile something larger (a smallish 3 module 
C++ program that links in functions from a 10
module C lib) things fall apart.  Program fails
with the usual windows page fault, and when I
try to trace down into the offending routine,
the debugger bounces around skipping lines.

Has anybody seen these before?  Compiling C
in debug mode, and then when tracing thru it
the debugger skips executable lines or somehow
gets out of sync with the souce?

And yes, I have optimizations turned off.

Thanks for any info anybody has on this.
I really would like to switch to Digital Mars,
but it isn't looking too promising at this point.
May 12 2003
↑ ↓ → "Walter" <walter digitalmars.com> writes:
Try using windbg.exe on it. I find sometimes that different debuggers have
different characteristics that are helpful.

<rehjr optusnet.com.au> wrote in message
news:3EBF4E3D.EFA7E026 optusnet.com.au...
 I received my Digital Mars CD a few days ago,
 and have been beating my head against the wall
 trying to make it work.  It runs all right, and
 even compiles minimal programs.  But when I try
 to compile something larger (a smallish 3 module
 C++ program that links in functions from a 10
 module C lib) things fall apart.  Program fails
 with the usual windows page fault, and when I
 try to trace down into the offending routine,
 the debugger bounces around skipping lines.

 Has anybody seen these before?  Compiling C
 in debug mode, and then when tracing thru it
 the debugger skips executable lines or somehow
 gets out of sync with the souce?

 And yes, I have optimizations turned off.

 Thanks for any info anybody has on this.
 I really would like to switch to Digital Mars,
 but it isn't looking too promising at this point.

May 12 2003