• Bill Baxter (10/10) May 28 2007 I ran into a problem the other day where ddbg 0.8.1 was telling me that
• Jascha Wetzel (8/20) Jun 04 2007 if you're using codeblocks, it happens rather frequently that CB messes
• Bill Baxter (6/13) Jun 04 2007 Nope it wasn't codeblocks. I was getting the line number from emacs and...
• Myron Alexander (2/9) Jun 07 2007 I have the same problem using ddbg from command line.
• Regan Heath (33/34) Jul 19 2007 I am getting the same sort of error but my situation is almost entirely
• Regan Heath (3/3) Jul 19 2007 Stopping CodeBlocks and starting it up again seems to have resolved all
• Jascha Wetzel (3/5) Jul 19 2007 CB has a couple of issues with the GDB integration (which also controls
• Simen Haugen (10/20) Aug 14 2007 I have also been having problems with this, but now I'm getting another
• Jascha Wetzel (2/12) Aug 14 2007 does that problem also occur when you debug the program on the command l...
• Simen Haugen (18/31) Aug 14 2007 Yup, command line too.
• Jascha Wetzel (12/33) Aug 14 2007 ddbg doesn't support absolute filenames, atm.
• Ary Manzana (9/33) Aug 14 2007 Will ddbg support it in the future? The easiest way from a "front-end to...
• Jascha Wetzel (2/11) Aug 14 2007 i have that on my todo list for the next release.
• Ary Manzana (2/14) Aug 14 2007 Sweet, thanks! I was about to add a ticket to Descent, but... ;-)
• Ary Manzana (4/30) Aug 14 2007 Can you send me the source code, or at least the hierarchy of the
• Simen Haugen (8/38) Aug 14 2007 The problem seems to be with ddbg.
• Jascha Wetzel (3/4) Aug 14 2007 if descent is issuing absolute filenames to ddbg, it's also a descent
• Simen Haugen (4/8) Aug 14 2007 It worked using the path from lsm. Descent outputs the full pathname whe...
• Jascha Wetzel (3/5) Aug 14 2007 k, i added it in the hints section of the documentation:
• Ary Manzana (2/7) Aug 14 2007 Ok, I'll fix that and try to release a patch as soon as possible.

Bill Baxter <dnewsgroup billbaxter.com> writes:

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 <firstname mainia.de> writes:

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

Bill Baxter <dnewsgroup billbaxter.com> writes:

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

Myron Alexander <someone somewhere.com> writes:

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.

Regan Heath <regan netmail.co.nz> writes:

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"

Soure file "E:\D\src\Sudoku\sudoku.d" not found

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

Regan Heath <regan netmail.co.nz> writes:

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

Regan

Jascha Wetzel <firstname mainia.de> writes:

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.

"Simen Haugen" <simen norstat.no> writes:

I have also been having problems with this, but now I'm getting another 
error using ddbg 0.10, descent 0.4, rebuild 0.70 and dmd 1.020
->Soure file "C:\projects\nsd\src\nsd.d" not found

Everything was working perfectly, but suddenly it stopped working. I've been 
debugging this project before, but after writing more code (no more files or 
anything) it just couldn't find the files anymore.

The strange thing is that it is not happening for all the files in the 
project, just a couple of them...


"Bill Baxter" <dnewsgroup billbaxter.com> wrote in message 
news:f3fpmd$2iis$1 digitalmars.com...
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 <"[firstname]" mainia.de> writes:

Simen Haugen wrote:
 I have also been having problems with this, but now I'm getting another 
 error using ddbg 0.10, descent 0.4, rebuild 0.70 and dmd 1.020
 ->Soure file "C:\projects\nsd\src\nsd.d" not found
 
 Everything was working perfectly, but suddenly it stopped working. I've been 
 debugging this project before, but after writing more code (no more files or 
 anything) it just couldn't find the files anymore.
 
 The strange thing is that it is not happening for all the files in the 
 project, just a couple of them...

does that problem also occur when you debug the program on the command line?

"Simen Haugen" <simen norstat.no> writes:

Yup, command line too.

C:\projects\nsdata\bin\Debug>ddbg sps2nsd.exe
Ddbg 0.10 beta - D Debugger
Copyright (c) 2007 Jascha Wetzel
see http://ddbg.mainia.de/doc.html for documentation

Loading symbols from sps2nsd.exe
->bp c:\projects\nsdata\src\nsd\nsd.d:1361
Soure file "c:\projects\nsdata\src\nsd\nsd.d" not found
->^C

C:\projects\nsdata\bin\Debug>dir c:\projects\nsdata\src\nsd\nsd.d
 Volume in drive C is Partition_1
 Volume Serial Number is 047C-6206

 Directory of c:\projects\nsdata\src\nsd

14.08.2007  15:24            37 902 nsd.d
               1 File(s)         37 902 bytes
               0 Dir(s)     804 540 416 bytes free



"Jascha Wetzel" <"[firstname]" mainia.de> wrote in message 
news:f9s52g$8mo$1 digitalmars.com...
 Simen Haugen wrote:
 I have also been having problems with this, but now I'm getting another 
 error using ddbg 0.10, descent 0.4, rebuild 0.70 and dmd 1.020
 ->Soure file "C:\projects\nsd\src\nsd.d" not found

 Everything was working perfectly, but suddenly it stopped working. I've 
 been debugging this project before, but after writing more code (no more 
 files or anything) it just couldn't find the files anymore.

 The strange thing is that it is not happening for all the files in the 
 project, just a couple of them...

 does that problem also occur when you debug the program on the command 
 line? 

Jascha Wetzel <"[firstname]" mainia.de> writes:

Simen Haugen wrote:
 Yup, command line too.
 
 C:\projects\nsdata\bin\Debug>ddbg sps2nsd.exe
 Ddbg 0.10 beta - D Debugger
 Copyright (c) 2007 Jascha Wetzel
 see http://ddbg.mainia.de/doc.html for documentation
 
 Loading symbols from sps2nsd.exe
 ->bp c:\projects\nsdata\src\nsd\nsd.d:1361
 Soure file "c:\projects\nsdata\src\nsd\nsd.d" not found
 ->^C
 
 C:\projects\nsdata\bin\Debug>dir c:\projects\nsdata\src\nsd\nsd.d
  Volume in drive C is Partition_1
  Volume Serial Number is 047C-6206
 
  Directory of c:\projects\nsdata\src\nsd
 
 14.08.2007  15:24            37 902 nsd.d
                1 File(s)         37 902 bytes
                0 Dir(s)     804 540 416 bytes free

ddbg doesn't support absolute filenames, atm.
use lsm to list the source modules as they are saved in the executable 
and use these names (or substrings of them) to set the breakpoints.
in order to find the (relative) source module paths, you need to set the 
search path.
assuming you compiled in c:\projects\nsdata\ and you're executing in 
c:\projects\nsdata\bin\Debug the following should work:
sp ..\..
bp src\nsd\nsd.d:1361

or, as a shortcut:
bp nsd.d:1361

Ary Manzana <ary esperanto.org.ar> writes:

Jascha Wetzel escribió:
 Simen Haugen wrote:
 Yup, command line too.

 C:\projects\nsdata\bin\Debug>ddbg sps2nsd.exe
 Ddbg 0.10 beta - D Debugger
 Copyright (c) 2007 Jascha Wetzel
 see http://ddbg.mainia.de/doc.html for documentation

 Loading symbols from sps2nsd.exe
 ->bp c:\projects\nsdata\src\nsd\nsd.d:1361
 Soure file "c:\projects\nsdata\src\nsd\nsd.d" not found
 ->^C

 C:\projects\nsdata\bin\Debug>dir c:\projects\nsdata\src\nsd\nsd.d
  Volume in drive C is Partition_1
  Volume Serial Number is 047C-6206

  Directory of c:\projects\nsdata\src\nsd

 14.08.2007  15:24            37 902 nsd.d
                1 File(s)         37 902 bytes
                0 Dir(s)     804 540 416 bytes free

 
 ddbg doesn't support absolute filenames, atm.

Will ddbg support it in the future? The easiest way from a "front-end to 
ddbg" point is to just configure the source paths, pass the absoulte 
filename, and let ddbg figure the relative path. Otherwise all 
front-ends will end up having this algorithm (duplicated) instead of 
having it in one place (the debugger).

Also from a command-line point this is useful: instead of having the 
user "calculate" the relative path, she could copy the absoulte path and 
let ddbg figure it out.

Jascha Wetzel <"[firstname]" mainia.de> writes:

Ary Manzana wrote:
 Will ddbg support it in the future? The easiest way from a "front-end to 
 ddbg" point is to just configure the source paths, pass the absoulte 
 filename, and let ddbg figure the relative path. Otherwise all 
 front-ends will end up having this algorithm (duplicated) instead of 
 having it in one place (the debugger).
 
 Also from a command-line point this is useful: instead of having the 
 user "calculate" the relative path, she could copy the absoulte path and 
 let ddbg figure it out.

i have that on my todo list for the next release.

Ary Manzana <ary esperanto.org.ar> writes:

Jascha Wetzel escribió:
 Ary Manzana wrote:
 Will ddbg support it in the future? The easiest way from a "front-end 
 to ddbg" point is to just configure the source paths, pass the 
 absoulte filename, and let ddbg figure the relative path. Otherwise 
 all front-ends will end up having this algorithm (duplicated) instead 
 of having it in one place (the debugger).

 Also from a command-line point this is useful: instead of having the 
 user "calculate" the relative path, she could copy the absoulte path 
 and let ddbg figure it out.

 
 i have that on my todo list for the next release.

Sweet, thanks! I was about to add a ticket to Descent, but... ;-)

Ary Manzana <ary esperanto.org.ar> writes:

Can you send me the source code, or at least the hierarchy of the 
project with stub functions? That way we'll see if it's a problem with 
ddbg or with Descent.

Simen Haugen wrote:
 I have also been having problems with this, but now I'm getting another 
 error using ddbg 0.10, descent 0.4, rebuild 0.70 and dmd 1.020
 ->Soure file "C:\projects\nsd\src\nsd.d" not found
 
 Everything was working perfectly, but suddenly it stopped working. I've been 
 debugging this project before, but after writing more code (no more files or 
 anything) it just couldn't find the files anymore.
 
 The strange thing is that it is not happening for all the files in the 
 project, just a couple of them...
 
 
 "Bill Baxter" <dnewsgroup billbaxter.com> wrote in message 
 news:f3fpmd$2iis$1 digitalmars.com...
 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 

"Simen Haugen" <simen norstat.no> writes:

The problem seems to be with ddbg.

Btw, Descent is great!
I was using Code::Blocks for some time before, but it was crashing 
sometimes, other times it seemed the parser hung (didn't help with restart). 
The symbol browser didn't work nice. No rebuild support. Highlighting was 
outdated. Probably a lot of other things I can't remember right now too.

"Ary Manzana" <ary esperanto.org.ar> wrote in message 
news:f9s6ah$h4q$1 digitalmars.com...
 Can you send me the source code, or at least the hierarchy of the project 
 with stub functions? That way we'll see if it's a problem with ddbg or 
 with Descent.

 Simen Haugen wrote:
 I have also been having problems with this, but now I'm getting another 
 error using ddbg 0.10, descent 0.4, rebuild 0.70 and dmd 1.020
 ->Soure file "C:\projects\nsd\src\nsd.d" not found

 Everything was working perfectly, but suddenly it stopped working. I've 
 been debugging this project before, but after writing more code (no more 
 files or anything) it just couldn't find the files anymore.

 The strange thing is that it is not happening for all the files in the 
 project, just a couple of them...


 "Bill Baxter" <dnewsgroup billbaxter.com> wrote in message 
 news:f3fpmd$2iis$1 digitalmars.com...
 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 <"[firstname]" mainia.de> writes:

Simen Haugen wrote:
 The problem seems to be with ddbg.

if descent is issuing absolute filenames to ddbg, it's also a descent 
problem - it shouldn't.

"Simen Haugen" <simen norstat.no> writes:

It worked using the path from lsm. Descent outputs the full pathname when as 
I printed on the command line.


"Jascha Wetzel" <"[firstname]" mainia.de> wrote in message 
news:f9scg4$1iv3$1 digitalmars.com...
 Simen Haugen wrote:
 The problem seems to be with ddbg.

 if descent is issuing absolute filenames to ddbg, it's also a descent 
 problem - it shouldn't. 

Jascha Wetzel <"[firstname]" mainia.de> writes:

Simen Haugen wrote:
 It worked using the path from lsm. Descent outputs the full pathname when as 
 I printed on the command line.

k, i added it in the hints section of the documentation:
http://ddbg.mainia.de/doc.html#hints

Ary Manzana <ary esperanto.org.ar> writes:

Jascha Wetzel wrote:
 Simen Haugen wrote:
 The problem seems to be with ddbg.

 
 if descent is issuing absolute filenames to ddbg, it's also a descent 
 problem - it shouldn't.

Ok, I'll fix that and try to release a patch as soon as possible.