www.digitalmars.com         C & C++   DMDScript  

digitalmars.D.debugger - DMD sometimes generates faulty debug lines information

reply Jascha Wetzel <"[firstname]" mainia.de> writes:
Everyone using Ddbg with larger than tiny test-programs has probably
experienced this.
What you'll notice is, that although you set a breakopint at some line x
(and the breakpoint is actually set at that line, not just skipping
non-instruction lines), the debugger will break at some other line y > x.
This and similar behaviour has been observed in larger programs (usually
with a lot of modules). I'm currently trying to narrow it down to a test
case, but without success, so far. I'll have to downsize my larger
project step by step...

Has anyone seen something like this in as-small-as-possible programs?
Mar 14 2007
next sibling parent reply Simen <simen.haugen pandavre.com> writes:
I don't know if its related, but in my current project ddbg stopped working
with breakpoints altogether:

Command-line: C:\ddbg\ddbg_gdb.exe -nx -fullname  -quiet -args
bin/Debug/TestTopline.exe
Working dir : C:\Documents and Settings\simen\My Documents\Projects\TestTopline\
 set prompt >>>>>>cb_gdb:

Copyright (c) 2007 Jascha Wetzel http://ddbg.mainia.de/ (gdb) >>>>>>cb_gdb:
 show version
cb_gdb:





cb_gdb:





cb_gdb:





cb_gdb:





cb_gdb:





cb_gdb:





cb_gdb:





cb_gdb:





cb_gdb:





cb_gdb:





cb_gdb:





cb_gdb:





cb_gdb:






cb_gdb:






cb_gdb:






Jascha Wetzel <[firstname] mainia.de> Wrote:
 Everyone using Ddbg with larger than tiny test-programs has probably
 experienced this.
 What you'll notice is, that although you set a breakopint at some line x
 (and the breakpoint is actually set at that line, not just skipping
 non-instruction lines), the debugger will break at some other line y > x.
 This and similar behaviour has been observed in larger programs (usually
 with a lot of modules). I'm currently trying to narrow it down to a test
 case, but without success, so far. I'll have to downsize my larger
 project step by step...
 
 Has anyone seen something like this in as-small-as-possible programs?

Mar 16 2007
parent Jascha Wetzel <"[firstname]" mainia.de> writes:
this problem probably has the same cause.
could you try 0.0.5, and tell me if the problem persists?

Simen wrote:
 I don't know if its related, but in my current project ddbg stopped working
with breakpoints altogether:
 
 Command-line: C:\ddbg\ddbg_gdb.exe -nx -fullname  -quiet -args
bin/Debug/TestTopline.exe
 Working dir : C:\Documents and Settings\simen\My
Documents\Projects\TestTopline\
 set prompt >>>>>>cb_gdb:

Copyright (c) 2007 Jascha Wetzel http://ddbg.mainia.de/ (gdb) >>>>>>cb_gdb:
 show version
 cb_gdb:





 cb_gdb:





 cb_gdb:





 cb_gdb:





 cb_gdb:





 cb_gdb:





 cb_gdb:





 cb_gdb:





 cb_gdb:





 cb_gdb:





 cb_gdb:





 cb_gdb:





 cb_gdb:






 cb_gdb:






 cb_gdb:






Jascha Wetzel <[firstname] mainia.de> Wrote:
 Everyone using Ddbg with larger than tiny test-programs has probably
 experienced this.
 What you'll notice is, that although you set a breakopint at some line x
 (and the breakpoint is actually set at that line, not just skipping
 non-instruction lines), the debugger will break at some other line y > x.
 This and similar behaviour has been observed in larger programs (usually
 with a lot of modules). I'm currently trying to narrow it down to a test
 case, but without success, so far. I'll have to downsize my larger
 project step by step...

 Has anyone seen something like this in as-small-as-possible programs?


Mar 20 2007
prev sibling parent Jascha Wetzel <"[firstname]" mainia.de> writes:
this is solved in Ddbg 0.0.5
I was wrong - DMD's codeview info for source lines is fine.

Jascha Wetzel wrote:
 Everyone using Ddbg with larger than tiny test-programs has probably
 experienced this.
 What you'll notice is, that although you set a breakopint at some line x
 (and the breakpoint is actually set at that line, not just skipping
 non-instruction lines), the debugger will break at some other line y > x.
 This and similar behaviour has been observed in larger programs (usually
 with a lot of modules). I'm currently trying to narrow it down to a test
 case, but without success, so far. I'll have to downsize my larger
 project step by step...
 
 Has anyone seen something like this in as-small-as-possible programs?

Mar 20 2007