[wingide-users] Is there a easy way to fix errors using C code extensions/DLLs

Hi,

That's odd... it sounds to me like this DLL may be manufacturing Python
code objects on the fly and setting the co_filename attribute on them to
the DLL file name.  Wing's debugger cannot trace through any C or C++
extension code because it has no concept of C stack frames, etc.  But it
will try to step through any Python bytecode that gets executed and will
attempt to show the file that's listed in the co_filename.

This hasn't come up as a problem before, so there's no way to block
opening of certain files.  To solve the problem, we may need to make a
patch to allow you to give some sort of list of exclude patterns via a
preference.  However, if you have any more info about what DLL this is, or
can share the source code for it with us, I'd like to better understand
why this is happening.

As always, please send any email with attachments or confidential info to
support@wingide.com and not to this mailing list.

Thanks for reporting this.

Stephan Deibel

--
Wing IDE for Python
Archaeopteryx Software, Inc
Take Flight!

www.wingide.com

On Tue, 21 Oct 2003 jason@dec.ilan.com wrote:

> When using Wing with code that imports a DLL containing extension code
> written in C.  Trouble happens in the debugger on the Windows platform.
> Wing will try to open the xxx.dll file as a text file to view it I guess
> and  ... you can guess what happens... it basically gets hosed.
> 
> Is there anyway to tell it "hey this has no source code to display"
> just step over it. like a C compiler will do for code that has no
> source code...
> 
> -thanks.
>