On 5 February 2014 16:55, Rainer Schuetze <r.sagitario@gmx.de> wrote:

>
>
> On 04.02.2014 18:47, ParticlePeter wrote:
>
>> On Wednesday, 13 November 2013 at 06:48:44 UTC, Rainer Schuetze wrote:
>>
>>>
>>>
>>> On 12.11.2013 10:19, evilrat wrote:
>>>
>>>> On Tuesday, 12 November 2013 at 08:06:24 UTC, Rainer Schuetze wrote:
>>>>
>>>>> If you switch the debugger to "Mago", the conversion is no longer needed, so you can still build and debug Win32 executables.
>>>>>
>>>>
>>>> mago gives "cannot launch debugger on %appname%. hr = 897...", so only x64 debugger left for usage
>>>>
>>>
>>> Are you sure that you are not trying to debug a 64-bit executable with mago? Maybe the working directory is invalid, this can also cause problems.
>>>
>>> If it still fails, please show the full error code, maybe I can guess what's going wrong.
>>>
>>
>> Are there any news on that issue ?
>> I get the same error Messages as mentioned with these debuggers:
>> VS and VS (x86 Mixed Mode) OUTPUT: AppName.pdb: cannot load PDB helper DLL
>> Mago WIN ERROR MESSAGE: cannot launch debugger on AppNamel.exe hr =
>> 89710016
>>
>> AppName is a 32-Bit executable.
>>
>> Its on a fresh installed Win 8 with VS2013, unfortunately no old VS2012 dlls available. Would it help to upgrade to Win 8.1 ?
>>
>>
>
> Have you tried the latest beta version [1]? This had some improvements in cv2pdb to find the ms*pdb.dll and some fixes in mago aswell.
>
> Launching a program with a non-existing working directory causes this problem, too. Maybe you have made a typo there?
>
> [1] https://github.com/D-Programming-Language/visuald/releases
>

Any chance you can release a beta with that settings bug fixed?
I've supervised 2 new VD installs the last couple of days, and they all
suffer the problem with the mspdb dll path not being remembered in the exe
path settings.

Am 05.02.2014 13:21, schrieb Manu:
> Any chance you can release a beta with that settings bug fixed?
> I've supervised 2 new VD installs the last couple of days, and they all
> suffer the problem with the mspdb dll path not being remembered in the
> exe path settings.

Temporary workaround:

http://stuff.benjamin-thaut.de/D/visualdfix.reg

Download and run. This is for visual studio 2010. If you need it for a different version you have to open it with a text editor and change "10.0" to "11.0" for 2012 and "12.0" for 2013.

Kind Regards
Benjamin Thaut

On 05.02.2014 13:21, Manu wrote:
>
> Any chance you can release a beta with that settings bug fixed?
> I've supervised 2 new VD installs the last couple of days, and they all
> suffer the problem with the mspdb dll path not being remembered in the
> exe path settings.

I didn't have a lot of time lately, but I am close to recovering from the recent SSD crash and almost have a working system back up now (with a precise GC dmd). I really should have pushed branches more often to github...

I have that settings bug fixed (saving to an registry entry but reading back a different one), so I hope I can create the new beta within the next couple of days.

On 05.02.2014 14:20, Benjamin Thaut wrote:
> Am 05.02.2014 13:21, schrieb Manu:
>> Any chance you can release a beta with that settings bug fixed?
>> I've supervised 2 new VD installs the last couple of days, and they all
>> suffer the problem with the mspdb dll path not being remembered in the
>> exe path settings.
>
> Temporary workaround:
>
> http://stuff.benjamin-thaut.de/D/visualdfix.reg

The x64 settings that go wrong are ExeSearchPath64 and LibSearchPath64. They are written to DMD.ExeSearchPath64 and DMD.LibSearchPath64 instead, so if you copy/rename those entries in the registry hive pointed to by Benjamin, that should be picked up with the next start.


>
> Download and run. This is for visual studio 2010. If you need it for a
> different version you have to open it with a text editor and change
> "10.0" to "11.0" for 2012 and "12.0" for 2013.
>
> Kind Regards
> Benjamin Thaut

On 05.02.2014 22:47, Rainer Schuetze wrote:
>
>
> On 05.02.2014 13:21, Manu wrote:
>>
>> Any chance you can release a beta with that settings bug fixed?
>> I've supervised 2 new VD installs the last couple of days, and they all
>> suffer the problem with the mspdb dll path not being remembered in the
>> exe path settings.
>
> I didn't have a lot of time lately, but I am close to recovering from
> the recent SSD crash and almost have a working system back up now (with
> a precise GC dmd). I really should have pushed branches more often to
> github...
>
> I have that settings bug fixed (saving to an registry entry but reading
> back a different one), so I hope I can create the new beta within the
> next couple of days.

The new beta 0.3.38beta3 of Visual D is available here: https://github.com/D-Programming-Language/visuald/releases