Clarification:
running an invoke() at *any* time will cause all subsequent tracing to segfault. Thus
(pseudoPASM):
loadlib ....
dlfunc ....
invoke
trace 1
end
Will cause the segfault.
> ------------Original Message-------------
> From: "Clinton A. Pierce" (via RT) <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]
> Date: Sun, Jun-15-2003 11:06 AM
> Subject: [perl #22706] IMCC (& Parrot) crash with -t when invoke is run
>
> # New Ticket Created by "Clinton A. Pierce"
> # Please include the string: [perl #22706]
> # in the subject line of all future correspondence about this issue.
> # <URL: http://rt.perl.org/rt2/Ticket/Display.html?id=22706 >
>
>
> Running imcc -t or parrot -t over an invoke instruction causes the programs
> to segfault. This happens under Win32. I do not have a platform
> independant example.
>
> .sub _win32_setup # void win32_setup(void)
> saveall
> loadlib P1, "kernel32.dll"
> dlfunc P0, P1, "GetStdHandle", "pi"
> set I0, 1
> set I5, -11
> invoke # Will crash here.
> store_global "kernel32", P1
> store_global "Win32handle", P5
> restoreall
> ret
> .end
>
>
>
>
>
>
