|
From: SourceForge.net <no...@so...> - 2005-05-13 10:14:24
|
Bugs item #1201289, was opened at 2005-05-13 03:14 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=1201289&group_id=78018 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Kevin Gadd (janusfury) Assigned to: Nobody/Anonymous (nobody) Summary: Exception handling code generates malformed EXCEPINFO struct Initial Comment: In ErrorUtils.cpp, the PyCom_ExcepInfoFromPyException function does not zero out the EXCEPINFO structure with ZeroMemory or memset before filling in the data elements, and it does not fill all of them in. Because of this, the Python Active Scripting interface sends malformed errors to script hosts. In particular, the pfnDeferredFillIn member of the EXCEPINFO struct contains a random value. This member is a function pointer, and according to MS's documentation, the only way to prevent it from being called is to assign it a NULL value. The particular script hosting implementation I use attempts to call this pointer upon recieving any and all Python script errors, and the only fix I've been able to come up with is to ignore the field outright (which probably is not correct). If this behavior is by design, any suggestions on a scripting host hack for dealing with this would be appreciated, so I can pass them on to the scripting host's author. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=551954&aid=1201289&group_id=78018 |
