• Bill Baxter <dnewsgroup billbaxter.com> May 28 2007
• Jascha Wetzel <firstname mainia.de> Jun 04 2007
• Bill Baxter <dnewsgroup billbaxter.com> Jun 04 2007
• Myron Alexander <someone somewhere.com> Jun 07 2007
• Regan Heath <regan netmail.co.nz> Jul 19 2007
• Regan Heath <regan netmail.co.nz> Jul 19 2007
• Jascha Wetzel <firstname mainia.de> Jul 19 2007

I ran into a problem the other day where ddbg 0.8.1 was telling me that 
it couldn't find line xxx of file yyy.  But it knew there was a file 
yyy.  It listed it in the modules list.

Don't have time to narrow it down to a repro right now, but just wanted 
to see if anyone else had seen this.  The source file in question was 
called OptMesh.d and I was running the debugger from a \data directory 
beneath that.  It was finding the other files fine, so my thought was 
maybe there's a bug with mixed case filenames.  The files that were 
working were all lowercase.  Maybe just a coincidence, though.

--bb

if you're using codeblocks, it happens rather frequently that CB messes 
up the linenumbers of breakpoints and issues them at some very high 
linenumber that doesn't exist.
if you find that the linenumber ddbg is complaining about doesn't exist, 
it's probably this problem.
else i'll need to reproduce this situation.
i haven't seen any problem concerning case of filenames, yet.

Bill Baxter wrote:
 I ran into a problem the other day where ddbg 0.8.1 was telling me that 
 it couldn't find line xxx of file yyy.  But it knew there was a file 
 yyy.  It listed it in the modules list.
 
 Don't have time to narrow it down to a repro right now, but just wanted 
 to see if anyone else had seen this.  The source file in question was 
 called OptMesh.d and I was running the debugger from a \data directory 
 beneath that.  It was finding the other files fine, so my thought was 
 maybe there's a bug with mixed case filenames.  The files that were 
 working were all lowercase.  Maybe just a coincidence, though.
 
 --bb

Jascha Wetzel wrote:
 if you're using codeblocks, it happens rather frequently that CB messes 
 up the linenumbers of breakpoints and issues them at some very high 
 linenumber that doesn't exist.


Nope it wasn't codeblocks.  I was getting the line number from emacs and 
typing it in at the ddbg command prompt.

 if you find that the linenumber ddbg is complaining about doesn't exist, 
 it's probably this problem.
 else i'll need to reproduce this situation.
 i haven't seen any problem concerning case of filenames, yet.


Ok.  I'll keep my eyes open for it happening in a little more compact 
sample.

--bb

Bill Baxter wrote:
 Jascha Wetzel wrote:
 if you're using codeblocks, it happens rather frequently that CB 
 messes up the linenumbers of breakpoints and issues them at some very 
 high linenumber that doesn't exist.


 Nope it wasn't codeblocks.  I was getting the line number from emacs and 
 typing it in at the ddbg command prompt.


I have the same problem using ddbg from command line.

I am getting the same sort of error but my situation is almost entirely 
different :)

I'm using code::blocks.  I have:

E:\Program Files\CodeBlocks
E:\D\DMD
E:\D\DMC
E:\D\DMD\BIN    <-ddbg installed here
E:\D\src

I followed the directions on the ddbg site to setup the debugger etc.

I created a new project in CodeBlocks:

E:\D\src\Sudoku\

adding 1 file

E:\D\src\Sudoku\sudoku.d

which I open and add 1 breakpoint, then I run and get:

 break "E:/D/src/Sudoku/sudoku.d:5"



in the Debugger(debug) window and it does not stop on the breakpoint.

The interesting thing is that in command prompt the path 
"E:/D/src/Sudoku/sudoku.d" cannot be found, but changing one path set 
from / to \ and it can!

C:\Development>dir "E:/D/src/Sudoku/sudoku.d"
  Volume in drive E is REMOVABLE
  Volume Serial Number is 9C9D-85FE

  Directory of E:\D\src\Sudoku

File Not Found

C:\Development>dir "E:/D/src/Sudoku\sudoku.d"
  Volume in drive E is REMOVABLE
  Volume Serial Number is 9C9D-85FE

  Directory of E:\D\src\Sudoku

19/07/2007  10:24             5,782 sudoku.d
                1 File(s)          5,782 bytes
                0 Dir(s)     131,833,856 bytes free


The line number ":5" is correct.

Regan

Stopping CodeBlocks and starting it up again seems to have resolved all 
the problems, weird!

Regan

Regan Heath wrote:
 Stopping CodeBlocks and starting it up again seems to have resolved all 
 the problems, weird!


CB has a couple of issues with the GDB integration (which also controls 
Ddbg). When in doubt, try reproducing the problem on the Ddbg command line.