RE: [Haskell] ANNOUNCE: Visual Haskell 0.2 final
From: haskell-bounces@haskell.org [mailto:haskell-bounces@haskell.org] On Behalf Of Krasimir Angelov
The final version of Visual Haskell 0.2 is ready:
http://www.haskell.org/visualhaskell
This is the first version that is: - available for both VStudio 2003 and VStudio 2005 - distributed with a stable GHC version (6.6) - the plugin itself is much more stable than its first 0.0 version
I'm trying to use this, but it seems to hang whenever I try to do a build (or a clean). Is there some way I can debug it to see why/where it's stuck? There's no build output in the output window. Alistair ***************************************************************** Confidentiality Note: The information contained in this message, and any attachments, may contain confidential and/or privileged material. It is intended solely for the person(s) or entity to which it is addressed. Any review, retransmission, dissemination, or taking of any action in reliance upon this information by persons or entities other than the intended recipient(s) is prohibited. If you received this in error, please contact the sender and delete the material from any computer. *****************************************************************
This usually happens when there is an uncaught Haskell exception. In
this case the RTS shows it in a message box. The problem is that with
threaded RTS the running thread might be different from the main
thread and in this case you can't see the message. Instead you have to
use the Spy++ tool distributed with Visual Studio. Look for a message
box with title "vs_haskell.dll" and see the message inside it.
Krasimir
On 12/11/06, Bayley, Alistair
From: haskell-bounces@haskell.org [mailto:haskell-bounces@haskell.org] On Behalf Of Krasimir Angelov
The final version of Visual Haskell 0.2 is ready:
http://www.haskell.org/visualhaskell
This is the first version that is: - available for both VStudio 2003 and VStudio 2005 - distributed with a stable GHC version (6.6) - the plugin itself is much more stable than its first 0.0 version
I'm trying to use this, but it seems to hang whenever I try to do a build (or a clean). Is there some way I can debug it to see why/where it's stuck? There's no build output in the output window.
Alistair ***************************************************************** Confidentiality Note: The information contained in this message, and any attachments, may contain confidential and/or privileged material. It is intended solely for the person(s) or entity to which it is addressed. Any review, retransmission, dissemination, or taking of any action in reliance upon this information by persons or entities other than the intended recipient(s) is prohibited. If you received this in error, please contact the sender and delete the material from any computer. *****************************************************************
From: Krasimir Angelov [mailto:kr.angelov@gmail.com]
This usually happens when there is an uncaught Haskell exception. In this case the RTS shows it in a message box. The problem is that with threaded RTS the running thread might be different from the main thread and in this case you can't see the message. Instead you have to use the Spy++ tool distributed with Visual Studio. Look for a message box with title "vs_haskell.dll" and see the message inside it.
I don't see anything with title vs_haskell.dll in Spy++. Is is meant to be a child of the Visual Studio window? Any other suggestions? Alistair ***************************************************************** Confidentiality Note: The information contained in this message, and any attachments, may contain confidential and/or privileged material. It is intended solely for the person(s) or entity to which it is addressed. Any review, retransmission, dissemination, or taking of any action in reliance upon this information by persons or entities other than the intended recipient(s) is prohibited. If you received this in error, please contact the sender and delete the material from any computer. *****************************************************************
No. It should be toplevel window. Try Spy\Processes from the menu to
see only these windows that are part of devenv.
Krasimir
On 12/11/06, Bayley, Alistair
From: Krasimir Angelov [mailto:kr.angelov@gmail.com]
This usually happens when there is an uncaught Haskell exception. In this case the RTS shows it in a message box. The problem is that with threaded RTS the running thread might be different from the main thread and in this case you can't see the message. Instead you have to use the Spy++ tool distributed with Visual Studio. Look for a message box with title "vs_haskell.dll" and see the message inside it.
I don't see anything with title vs_haskell.dll in Spy++. Is is meant to be a child of the Visual Studio window?
Any other suggestions?
Alistair ***************************************************************** Confidentiality Note: The information contained in this message, and any attachments, may contain confidential and/or privileged material. It is intended solely for the person(s) or entity to which it is addressed. Any review, retransmission, dissemination, or taking of any action in reliance upon this information by persons or entities other than the intended recipient(s) is prohibited. If you received this in error, please contact the sender and delete the material from any computer. *****************************************************************
From: Krasimir Angelov [mailto:kr.angelov@gmail.com]
No. It should be toplevel window. Try Spy\Processes from the menu to see only these windows that are part of devenv.
OK. I assume that I'm only looking at the threads under DEVENV. There are 9 of them, and only one has any (lots) windows under it. I still don't see it under here. Alistair ***************************************************************** Confidentiality Note: The information contained in this message, and any attachments, may contain confidential and/or privileged material. It is intended solely for the person(s) or entity to which it is addressed. Any review, retransmission, dissemination, or taking of any action in reliance upon this information by persons or entities other than the intended recipient(s) is prohibited. If you received this in error, please contact the sender and delete the material from any computer. *****************************************************************
To: 'Krasimir Angelov'
No. It should be toplevel window. Try Spy\Processes from the menu to see only these windows that are part of devenv.
OK. I assume that I'm only looking at the threads under DEVENV. There are 9 of them, and only one has any (lots) windows under it. I still don't see it under here.
(shall we take this off-list?) I can start up another DEVENV, attach the debugger, and Break All. It shows me assembler: 7FFE02F8 add byte ptr [eax],al 7FFE02FA add byte ptr [eax],al 7FFE02FC add byte ptr [eax],al 7FFE02FE add byte ptr [eax],al 7FFE0300 mov edx,esp 7FFE0302 sysenter 7FFE0304 ret <== breakpoint here 7FFE0305 pushfd 7FFE0306 or dword ptr [esp],100h 7FFE030D popfd 7FFE030E ret 7FFE030F mov edx,esp 7FFE0311 syscall 7FFE0313 ret I can Continue, but pressing Break All simply returns me to the same spot. This is the call-stack:
7ffe0304() ntdll.dll!77f5c534() kernel32.dll!77e689a9() user32.dll!77d4915e() kernel32.dll!77e68bd7() vs_haskell.dll!64f94b21() vs_haskell.dll!64f96d53() vs_haskell.dll!64f8d9ed() vs_haskell.dll!64f8e64c() vs_haskell.dll!64f8a149() vs_haskell.dll!64f8a30a() vs_haskell.dll!64615ad8() vs_haskell.dll!64615a61() msenv.dll!50012291() msenv.dll!500128a5() msenv.dll!500127c4() msenv.dll!500133ca() msenv.dll!50012ba0() msenv.dll!500c9aa9() msenv.dll!500c776f() msenv.dll!500c41d7() uxtheme.dll!5ad73e01() user32.dll!77d48723() user32.dll!77d48765() uxtheme.dll!5ad8a6a3() uxtheme.dll!5ad8a670() user32.dll!77d4969a() user32.dll!77d49688() user32.dll!77d49700() uxtheme.dll!5ad73e01() uxtheme.dll!5ad8a6a3() uxtheme.dll!5ad8a670() uxtheme.dll!5ad71c65() uxtheme.dll!5ad71b71() uxtheme.dll!5ad71af6() msenv.dll!500bf8e3() msenv.dll!500bf8e3() msenv.dll!500bf902() msenv.dll!500ae2b2() msenv.dll!500ae468() msenv.dll!5000ac60() user32.dll!77d497ab() user32.dll!77d4ab7a() msenv.dll!5000ad19() msenv.dll!5007afa0() msenv.dll!500c0fe3() MSCTF.dll!7472a743() MSCTF.dll!7472ba32() user32.dll!77d48654() user32.dll!77d48723() user32.dll!77d4a0ec() user32.dll!77d4aa77() msenv.dll!500b2e03() MSO.DLL!30b5fd93() MSO.DLL!30b60261() MSO.DLL!30b5f546() msenv.dll!500c98f1() msenv.dll!500c9b9d() MSO.DLL!30c19ac6() MSO.DLL!30c19a1e() msenv.dll!500c9bd4() msenv.dll!500e12e0() ntdll.dll!77f5f70f() ntdll.dll!77f60f7f() kernel32.dll!77e69436() kernel32.dll!77e69448() devenv.exe!004088a8() devenv.exe!00406ed7() devenv.exe!00410032() ntdll.dll!77f7e45c() ntdll.dll!77f5f7ee() ntdll.dll!77f5f8ea() ntdll.dll!77f5f70f() ntdll.dll!77f5f70f() ntdll.dll!77f60f7f() kernel32.dll!77e69436() kernel32.dll!77e69448() devenv.exe!004055a1() devenv.exe!004055c2() devenv.exe!004055d8() devenv.exe!004077bc() devenv.exe!0040780e() shlwapi.dll!70a7411b() kernel32.dll!77e735dd() shlwapi.dll!70a7411b() kernel32.dll!77e735e8()
Alistair ***************************************************************** Confidentiality Note: The information contained in this message, and any attachments, may contain confidential and/or privileged material. It is intended solely for the person(s) or entity to which it is addressed. Any review, retransmission, dissemination, or taking of any action in reliance upon this information by persons or entities other than the intended recipient(s) is prohibited. If you received this in error, please contact the sender and delete the material from any computer. *****************************************************************
Krasimir Angelov wrote:
This usually happens when there is an uncaught Haskell exception. In this case the RTS shows it in a message box. The problem is that with threaded RTS the running thread might be different from the main thread and in this case you can't see the message. Instead you have to use the Spy++ tool distributed with Visual Studio. Look for a message box with title "vs_haskell.dll" and see the message inside it.
So it isn't possible to call MessageBox() from an arbitrary thread? Should we be doing something in the RTS to work around this? Cheers, Simon
participants (3)
-
Bayley, Alistair -
Krasimir Angelov -
Simon Marlow