<div dir="ltr">In your build tree, there should be a "vtkpython.exe" -- can you try it with that (instead of python.exe) and see if you get the same thing...?<div><br></div><div><br><br><div class="gmail_quote">On Fri, Sep 5, 2008 at 10:58 AM, Carl Trapani <span dir="ltr"><<a href="mailto:carl@skytopsoftware.com">carl@skytopsoftware.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">Hi David,<br>
<br>
Here's what I've done:<br>
<br>
1) Started Visual Studio 2008 and opened the VTK.sln solution.<br>
2) Set it to stop on access violation exceptions (Win32 Exceptions - c0000005 Access violation)<br>
3) Opened a command prompt, cd'd to dir where ImagePlaneWidget.py is located and ran<br>
<br>
python ImagePlaneWidget.py<br>
<br>
4) Got the following at command prompt:<div class="Ih2E3d"><br>
alloc: invalid block: 10089F90: 1 0<br>
<br>
This application has requested the Runtime to terminate it in an unusual way.<br>
Please contact the application's support team for more information.<br>
<br></div>
5) Then, a dialog prompted me to "Check online ..., Close, or Debug". I chose Debug and selected the already open instance of Visual Studio.<br>
<br>
6) Then, VS displays this dialog:<br>
<br>
First-chance exception at 0x0408579d in python.exe: 0xC0000005: Access violation reading location 0x000001b4.<br>
<br>
Break, Continue, Ignore, Pray, Start Drinking ...<br>
<br>
I selected Break. Then, I get a dialog warning that VS doesn't have the symbols for Tk85.dll - but I can't subsequently get that warning when I re-run, so I'm not sure of the detail. Anyway ... here is the Call Stack:<br>
<br>
> tk85.dll!03f3579d() [Frames below may be incorrect and/or missing, no symbols loaded for tk85.dll] tk85.dll!03ef4654() tk85.dll!03f9d6f7() ntdll.dll!76e6a604() ntdll.dll!76e3a303() ntdll.dll!76e5fea0() kernel32.dll!7575596c() kernel32.dll!756fd873() msvcrt.dll!768b2070() msvcrt.dll!768b1d5e() ntdll.dll!76e5fea0() ntdll.dll!76e62447() ntdll.dll!76e6214c() ntdll.dll!76e618c3() kernel32.dll!75707a7e() msvcr71.dll!7c34218a() ntdll.dll!76e618c3() kernel32.dll!75707a7e() msvcr71.dll!7c34218a() python25.dll!1e062ff6() python25.dll!1e0266dc() python25.dll!1e039eaa() python25.dll!1e041862() python25.dll!1e0266dc() python25.dll!1e03a32d() python25.dll!1e03b2e2() python25.dll!1e03d296() python25.dll!1e03e1bd() python25.dll!1e03e222() python25.dll!1e0abbda() python25.dll!1e0acb56() python25.dll!1e0ad22d() msvcr71.dll!7c369c33() python25.dll!1e08add6() python.exe!1d0011a5() kernel32.dll!75703833() ntdll.dll!76e3a9bd() <br>
Let me know if I can help further.<br>
Thanks!<br><font color="#888888">
Carl</font><div><div></div><div class="Wj3C7c"><br>
<br>
<br>
David Cole wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
It's likely a bug.<br>
<br>
Can you set your Visual Studio to stop on access violation exceptions, and the look at the call stack window and copy/paste/send along the call stack when it crashes...?<br>
(See the "Debug > Exceptions" menu item to stop on access violations and the "Debug > Windows > Call Stack" menu item to show the call stack... then select all the text in the call stack window and Ctrl+C to copy.)<br>
<br>
<br>
Thanks,<br>
David<br>
<br>
</blockquote>
<br>
</div></div></blockquote></div><br></div></div>