kicad-developers team mailing list archive
Mailing list archive
Re: Python-a-mingw-us Windows Debug Scripting Builds
On 31 August 2013 21:39, Dick Hollenbeck <dick@xxxxxxxxxxx> wrote:
> On 08/31/2013 03:00 PM, Brian Sidebotham wrote:
> >>> Q:
> > >>
> > >> (i) Does anyone see any output from the PyErr_Print() calls?
> > Try using a tool like Debug Viewer available from Microsoft. If
> > PyErr_Print() is anything like wxLogXXX(), on Windows the output is
> > to the OutputDebugString() function which does not end up on stdout.
> > You can find the debug viewer here:
> > http://technet.microsoft.com/en-us/sysinternals/bb896647.aspx
> > You must run the debug viewer as Administrator in order to see the
> > debugging strings.
> > GDB reports OutputDebugString() too on Windows. For example, I see
> output from the
> > wxLogXXX() function that reports setting the KISYSMOD environment
> variable. I suspect
> > PyErr_Print() just pipes to stderr or stdout.
> > Thanks,
> > Brian.
> Look at the source code. Start with line 1057 of pythonrun.c. That takes
> you to
> PyErr_PrintEx(), line 1151.
> hook = PySys_GetObject("excepthook")
> It seems you have to install a "excepthook" someplace before calling
> PyErr_Print(), at
> least somebody or something does.
I believe excepthook is simply set by the originating Exception. If it's
not set there there's nothing to print; In fact the Python API manual says
if you call PyErr_Print() without there having been an error it would
result in a fatal error!
On Windows, the failure for the scripting console is:
Traceback (most recent call last):
File "<string>", line 2, in <module>
8, in <module>
line 15, in <module>
line 8, in <module>
from wx import stc
File "D:\launchpad-dev\kicad-winbuilder\kicad\bin\pylib\wx\stc.py", line
10, in <module>
ImportError: DLL load failed on
specified module could not be found.
But I can assure you that this file is good and does work. I can step
through the code surrounding the script console generation and then it
works okay, only occasionally will it fail with the same message.
I can run up python normally and run pretty much the same code as an
example and see and use the PyCrust interactive scripting console. So I've
no idea why it's complaining.