Re: [dylan] Fun Windows question related to stack allocation in the spy

For what it is worth, I got PellesC going on this machine (VM) and it runs
fine there (including debugging).

The stack allocation error appears therefore to be related to linking with
Visual Studio 2012 rather than Pelles C or VC6.

I've identified other issues with the Windows build and have updated Trello
about that. Open Dylan is not reading / writing to the registry at the
correct location which results in some fun.

 - Bruce



On Wed, Jan 23, 2013 at 5:19 PM, Bruce Mitchener
<[email protected]>wrote:

> So ... I have a Dylan app linking with the Visual Studio 2012 linker on
> Windows 7 (32 bit).
>
> This isn't yet in a state where I'll be able to debug the exectuable, but
> I think I have a plan for that.
>
> However, when I try to launch the executable via the IDE, I get this error:
>
>         Error: Serious Error: Failed to allocate stack in Spy call on
> Thread ....
>
> This happens when this function returns NULL:
>
>
> https://github.com/dylan-lang/opendylan/blob/master/sources/runtime-manager/debugger-nub/x86-win32/remote_function_call.c#L97
>
> This happens almost immediately, so it isn't a result of the 30 second
> timeout that Andreas Bogk added many years ago.
>
> Is this perhaps a UAC issue? Disabling UAC doesn't fix this (unless I
> disabled it wrong).
>
> For those who might find this subject interesting, I have a public board
> in Trello that lists the issues that I've found so far in using OpenDylan
> 2012.1 on Windows:
>
>     https://trello.com/board/windows-support/50ffae107c44de1b1e001bf3
>
>  - Bruce
>
>

_______________________________________________
hackers mailing list
[email protected]
https://lists.opendylan.org/mailman/listinfo/hackers