• Daemon (35/35) Jun 13 2013 I am failing at getting the debugging in Code::Blocks to work on
• Daemon (1/1) Jun 13 2013 Nevermind, it's not worth it in the end.
• Geancarlo Rocha (2/2) Jun 13 2013 since you are on windows, you may want to try Visual
• Daemon (2/4) Jun 13 2013 Well, I am using Visual D and I was searching for alternatives.
• JN (2/7) Jun 14 2013 Try ddbg, I remember having limited success using it in C::B
• Ramon (21/26) Aug 27 2013 For what it's worth, I have written a small howto for code:blocks
• Dejan Lekic (3/5) Nov 11 2013 You are aware of the fact that VisualD does not work with the
• Rainer Schuetze (3/8) Nov 12 2013 It does not work with Visual Studio Express, but it works with the VS
• Dejan Lekic (1/4) Nov 19 2013 Thanks for the enlightenment Rainer! I did not know this! (obviously)

"Daemon" <Daemon yahoo.com> writes:

I am failing at getting the debugging in Code::Blocks to work on 
D applications. I have downloaded the GDB executable and set a 
path to it. Even though I ticked all the "generate debug 
symbols", it just recompiles and gives me this output:

Building to ensure sources are up-to-date
Selecting target:
Debug
Adding source dir: C:\Learning\Play\
Adding source dir: C:\Learning\Play\
Adding file: C:\Learning\Play\bin\Debug\Play.exe
Changing directory to: C:/Learning/Play/.
Set variable: 
PATH=.;C:\DMD2\windows\bin;C:\DMD2\windows;C:\dm\bin;C:\Windows\System32;C:\Windows;C:\Windows\System32\wbem;C:\Windows\System32\WindowsPowerS
ell\v1.0;C:\Program 
Files (x86)\Windows Kits\8.0\Windows Performance 
Toolkit;C:\Program Files\Microsoft SQL 
Server\110\Tools\Binn;C:\Program Files (x86)\ATI 
Technologies\ATI.ACE\Core-Static;C:\Program Files 
(x86)\Gtk-Runtime\bin;C:\Program Files\Gtk-Runtime\bin;C:\Program 
Files (x86)\Git\cmd;C:\Program Files 
(x86)\GtkSharp\2.12\bin;C:\DMD2\dmd2\windows\bin;C:\DMD2\dm\bin
Starting debugger: C:\Program Files (x86)\mingw\bin\gdb.exe -nx 
-fullname  -quiet  -args C:/Learning/Play/bin/Debug/Play.exe
done
Registered new type: wxString
Registered new type: STL String
Registered new type: STL Vector
Setting breakpoints
Debugger name and version: GNU gdb 5.2.1
No symbol table is loaded.  Use the "file" command.
Starting the debuggee failed: No executable specified, use 
`target exec'.
Debugger finished with status 0

I've read that I have to pass some flags to the debugger, but I 
have no idea how or what flags.

Any help would be appreciated

"Daemon" <Daemon yahoo.com> writes:

Nevermind, it's not worth it in the end.

"Geancarlo Rocha" <asdf mailinator.com> writes:

since you are on windows, you may want to try Visual 
D(http://www.dsource.org/projects/visuald/)

"Daemon" <Daemon yahoo.com> writes:

On Thursday, 13 June 2013 at 20:08:42 UTC, Geancarlo Rocha wrote:
 since you are on windows, you may want to try Visual 
 D(http://www.dsource.org/projects/visuald/)

Well, I am using Visual D and I was searching for alternatives.

"JN" <666total wp.pl> writes:

On Thursday, 13 June 2013 at 20:36:31 UTC, Daemon wrote:
 On Thursday, 13 June 2013 at 20:08:42 UTC, Geancarlo Rocha 
 wrote:
 since you are on windows, you may want to try Visual 
 D(http://www.dsource.org/projects/visuald/)

 Well, I am using Visual D and I was searching for alternatives.

Try ddbg, I remember having limited success using it in C::B

"Ramon" <spam thanks.no> writes:

On Thursday, 13 June 2013 at 20:36:31 UTC, Daemon wrote:
 On Thursday, 13 June 2013 at 20:08:42 UTC, Geancarlo Rocha 
 wrote:
 since you are on windows, you may want to try Visual 
 D(http://www.dsource.org/projects/visuald/)

 Well, I am using Visual D and I was searching for alternatives.

For what it's worth, I have written a small howto for code:blocks 
in the wiki here (under CodeBlocks) and it works properly (under 
linux, that is).

 From what little experience I have in running linux developed 
software on Windows, I always felt it to be a PITA. Quite 
probably the problems you experienced are related to that, too.

A word on CodeBlocks:

It's a nice IDE and it works plus or minus fine. But there are 
"buts":

- Debugging is limited insofar as strings and composite types 
can't be watched in the debugger.

- in the current release 12.11 the Code Blocks guys cut out - for 
whatever weird reason ever - the (very handy) local variables 
display.
In other words: If you want to use Code Blocks you should 
definitely use the old version 10.05.

I can't speak too loud in development in Windows (because I 
hardly use Windows and try to avoid it) but the advice given 
above sounds reasonable to me. Simply use Visual(whatever).

A+ - R

"Dejan Lekic" <dejan.lekic gmail.com> writes:

On Thursday, 13 June 2013 at 20:08:42 UTC, Geancarlo Rocha wrote:
 since you are on windows, you may want to try Visual 
 D(http://www.dsource.org/projects/visuald/)

You are aware of the fact that VisualD does not work with the 
free version of the Visual Studio, are you?

Rainer Schuetze <r.sagitario gmx.de> writes:

On 11.11.2013 13:37, Dejan Lekic wrote:
 On Thursday, 13 June 2013 at 20:08:42 UTC, Geancarlo Rocha wrote:
 since you are on windows, you may want to try Visual
 D(http://www.dsource.org/projects/visuald/)

 You are aware of the fact that VisualD does not work with the free
 version of the Visual Studio, are you?

It does not work with Visual Studio Express, but it works with the VS 
Shell (the IDE without support for MS supplied languages).

Dejan Lekic <dejan.lekic gmail.com> writes:

 
 It does not work with Visual Studio Express, but it works with the VS
 Shell (the IDE without support for MS supplied languages).

Thanks for the enlightenment Rainer! I did not know this! (obviously)