On Friday, 31 October 2014 at 11:02:29 UTC, Rainer Schuetze wrote:
>
>
> On 31.10.2014 11:31, Zaher Dirkey wrote:
>> Failed to install VS2010 i have links to download but icons not appears,
>> So i downloaded VS2080 and VisualD (VisualD in c:\programs\visuald),
>> Create new D project in c:\temp\testd (no spaces)
>> but then i have Error in compiling
>>
>> ------ Rebuild All started: Project: testd, Configuration: Debug Win32
>> ------
>> Building Debug\testd.exe...
>> "Debug\testd.exe_cv" not created!
>> Building Debug\testd.exe failed!
>> Details saved as
>> "file://c:\temp\testd\testd\testd\Debug\testd.buildlog.html"
>> ========== Rebuild All: 0 succeeded, 1 failed, 0 skipped

Yes i already moved it, to the path, not worked,
Now it is work after restating my computer and finally the debugger work for me, the strange about programming world.

VS2013 need win7, i have XP :(

Thank you

Also there is another problem i fixed, it is cv2pdb that come with VisualD, it is win64 so i installed original one form

http://dsource.org/projects/cv2pdb

On 31.10.2014 16:09, Zaher Dirkey wrote:
> Also there is another problem i fixed, it is cv2pdb that come with
> VisualD, it is win64 so i installed original one form
>
> http://dsource.org/projects/cv2pdb

Strange, the project does not even have an x64 configuration.

It seems building with VS2013 sets the "required OS version" to 6, which is too large for XP. I'll change this...

Thank you Rainer, yes, it is show me as not win32 error.
now it is work on 2008 like a charm.

On Friday, 31 October 2014 at 16:38:04 UTC, Rainer Schuetze wrote:
>
>
> On 31.10.2014 16:09, Zaher Dirkey wrote:
>> Also there is another problem i fixed, it is cv2pdb that come with
>> VisualD, it is win64 so i installed original one form
>>
>> http://dsource.org/projects/cv2pdb
>
> Strange, the project does not even have an x64 configuration.
>
> It seems building with VS2013 sets the "required OS version" to 6, which is too large for XP. I'll change this...

On Thursday, 16 October 2014 at 11:25:07 UTC, Zaher Dirkey wrote:
> Hi,
> I want to debug my application using gdb, i used last mingw version that include gdb7.6, i use CodeBlock as editor, but i notice gdb can't run my exe in windows xp(sp3), i added -gc to compiler but it fail to start gdb
>
> dmd -gc hello.d
> gdb hello.exe
>
> If it work it will work with CodeBlock debugger for windows.
>
> If not it is supported what should i use? CodeBlock have another option CDB, from where i can install it?
>
> thanks in advance.

Hi, look at this too:

http://forum.dlang.org/thread/dds1ei$2ff9$1@digitaldaemon.com?page=2#post-ddu63o:241h7v:241:40digitaldaemon.com

i've just tried today and even if it's been posted 10 years ago it still works.
CDB can be grabbed here:

http://download.cnet.com/Debugging-Tools-for-Windows/3000-2086_4-10907878.html

We need to add to the environment

_NT_SYMBOL_PATH=srv*c:\DownstreamStore*http://msdl.microsoft.com/download/symbols

//it just a note for my self

On Friday, 31 October 2014 at 15:09:48 UTC, Zaher Dirkey wrote:
> Also there is another problem i fixed, it is cv2pdb that come with VisualD, it is win64 so i installed original one form
>
> http://dsource.org/projects/cv2pdb

@ljkp
I retried with the CDB, Not worked, maybe i have bad configuration for cdb debugger in CodeBlock. do i need to add like Arguments or Initialization commands?

On Sunday, 2 November 2014 at 15:27:52 UTC, ljkp wrote:
> On Thursday, 16 October 2014 at 11:25:07 UTC, Zaher Dirkey wrote:
>> Hi,
>> I want to debug my application using gdb, i used last mingw version that include gdb7.6, i use CodeBlock as editor, but i notice gdb can't run my exe in windows xp(sp3), i added -gc to compiler but it fail to start gdb
>>
>> dmd -gc hello.d
>> gdb hello.exe
>>
>> If it work it will work with CodeBlock debugger for windows.
>>
>> If not it is supported what should i use? CodeBlock have another option CDB, from where i can install it?
>>
>> thanks in advance.
>
> Hi, look at this too:
>
> http://forum.dlang.org/thread/dds1ei$2ff9$1@digitaldaemon.com?page=2#post-ddu63o:241h7v:241:40digitaldaemon.com
>
> i've just tried today and even if it's been posted 10 years ago it still works.
> CDB can be grabbed here:
>
> http://download.cnet.com/Debugging-Tools-for-Windows/3000-2086_4-10907878.html

On 03.11.2014 15:31, Zaher Dirkey wrote:
> We need to add to the environment
>
> _NT_SYMBOL_PATH=srv*c:\DownstreamStore*http://msdl.microsoft.com/download/symbols
>

Do you mean this has an influence on using cv2pdb? I would be surprised.

For the Visual Studio debugger you can also set this path in Tools->Options->Debugging->Symbols. Newer versions of VS also have the symbol servers pre-configured.

On 03.11.2014 15:50, Zaher Dirkey wrote:
> @ljkp
> I retried with the CDB, Not worked, maybe i have bad configuration for
> cdb debugger in CodeBlock. do i need to add like Arguments or
> Initialization commands?
>

I'm not sure it was obvious but cdb is a command line version of the Microsoft windows debugger (windbg) and is not compatible with gdb.

Both windbg and cdb should work with dmd compiled executables (after conversion with cv2pdb for Win32), but I guess these have not been tried lately because the VS experience is so much better...

You might also be interested in switching the debug engine in the project settings to "Mago". This is a debug engine written for the D programming language, so, for example, you don't have to fall back to C syntax for watch expression.