On 06.08.2017 05:21, FoxyBrown wrote:
On Sunday, 6 August 2017 at 03:12:22 UTC, FoxyBrown wrote:
On Thursday, 3 August 2017 at 20:22:56 UTC, Johnson Jones wrote:
On Thursday, 3 August 2017 at 07:06:06 UTC, Rainer Schuetze wrote:
[...]
Thanks! Seems to be working.
well, in x86 I still get
On Sunday, 6 August 2017 at 03:12:22 UTC, FoxyBrown wrote:
On Thursday, 3 August 2017 at 20:22:56 UTC, Johnson Jones wrote:
On Thursday, 3 August 2017 at 07:06:06 UTC, Rainer Schuetze
wrote:
[...]
Thanks! Seems to be working.
well, in x86 I still get a few BP's that won't be hit every
once
On Thursday, 3 August 2017 at 20:22:56 UTC, Johnson Jones wrote:
On Thursday, 3 August 2017 at 07:06:06 UTC, Rainer Schuetze
wrote:
On 31.07.2017 19:51, Johnson Jones wrote:
On Saturday, 22 July 2017 at 12:54:17 UTC, Rainer Schuetze
wrote:
On 18.06.2017 20:25, Mike B Johnson wrote:
[...]
On Thursday, 3 August 2017 at 07:06:06 UTC, Rainer Schuetze wrote:
On 31.07.2017 19:51, Johnson Jones wrote:
On Saturday, 22 July 2017 at 12:54:17 UTC, Rainer Schuetze
wrote:
On 18.06.2017 20:25, Mike B Johnson wrote:
[...]
After installing VS2017 on a fresh Win10 install I could
reprod
On 31.07.2017 19:51, Johnson Jones wrote:
On Saturday, 22 July 2017 at 12:54:17 UTC, Rainer Schuetze wrote:
On 18.06.2017 20:25, Mike B Johnson wrote:
[...]
Didn't work ;/
All I get on the output wndow is
"
C:\Windows\System32\dbghelp.dll unloaded.
The thread 0x1ea4 has exited with code
On Saturday, 22 July 2017 at 12:54:17 UTC, Rainer Schuetze wrote:
On 18.06.2017 20:25, Mike B Johnson wrote:
[...]
Didn't work ;/
All I get on the output wndow is
"
C:\Windows\System32\dbghelp.dll unloaded.
The thread 0x1ea4 has exited with code -1 (0x).
The thread 0x1390 has exite
On 18.06.2017 20:25, Mike B Johnson wrote:
I could produce an issue when starting the mago debugger for the first
time after firing up VS2015: it showed an error, though, instead of
not doing anything at all. Maybe it's a different effect of the same
problem. I have added a work around that f
On 20.06.2017 02:05, Mike B Johnson wrote:
On Sunday, 18 June 2017 at 21:02:12 UTC, Rainer Schuetze wrote:
On 18.06.2017 20:25, Mike B Johnson wrote:
Didn't work ;/
All I get on the output wndow is
"
C:\Windows\System32\dbghelp.dll unloaded.
The thread 0x1ea4 has exited with code -1 (0xf
On Sunday, 18 June 2017 at 21:02:12 UTC, Rainer Schuetze wrote:
On 18.06.2017 20:25, Mike B Johnson wrote:
Didn't work ;/
All I get on the output wndow is
"
C:\Windows\System32\dbghelp.dll unloaded.
The thread 0x1ea4 has exited with code -1 (0x).
The thread 0x1390 has exited with co
On 18.06.2017 20:25, Mike B Johnson wrote:
Didn't work ;/
All I get on the output wndow is
"
C:\Windows\System32\dbghelp.dll unloaded.
The thread 0x1ea4 has exited with code -1 (0x).
The thread 0x1390 has exited with code -1 (0x).
The thread 0x1ac has exited with code -1 (0xf
On Sunday, 18 June 2017 at 17:43:20 UTC, Rainer Schuetze wrote:
On 18.06.2017 16:50, Rainer Schuetze wrote:
On 18.06.2017 16:17, Mike B Johnson wrote:
So, there is some issue with x64 and visual d's debugging in
visual studio. That is the only file in the project. If it
works on your syste
On 18.06.2017 16:50, Rainer Schuetze wrote:
On 18.06.2017 16:17, Mike B Johnson wrote:
So, there is some issue with x64 and visual d's debugging in visual
studio. That is the only file in the project. If it works on your
system, keep trying until it doesn't!
As you expected, its not simpl
On 18.06.2017 16:17, Mike B Johnson wrote:
So, there is some issue with x64 and visual d's debugging in visual
studio. That is the only file in the project. If it works on your
system, keep trying until it doesn't!
As you expected, its not simple to reproduce. I have not managed to do so.
C
in the last 20mins I did the following
1. Create a new DMD/LDC project
2. Added the code
import std.stdio;
import core.sys.windows.windows;
import std.array, std.conv;
int main(string[] argv)
{
wchar* pCmd = cast(wchar*)to!wstring(argv.join(" ")).ptr;
STARTUPINFO si;
14 matches
Mail list logo
