Threaded Cygwin Python Import Problem

Jason Tishler
Fri Jul 13 13:46:00 GMT 2001


On Sat, Jul 14, 2001 at 04:30:42AM +1000, Robert Collins wrote:
> ----- Original Message -----
> From: "Jason Tishler" <>
> > [Moved from cygwin-patches to cygwin-developers...]
> Sorry I'm slow getting to this one :[. Time has been against me this last
> month.

Only this month?  You are very lucky -- time has been against me for
years... :,)

> > On Tue, Jul 10, 2001 at 01:24:13PM +1000, Robert Collins wrote:
> > > >     python
> > >
> > > gdb.out: the event handle is clearly wrong. Can you include the output
> > > of print *this ? and list (so I know what the lines actually are :])>
> >
> > See attached gdb.out.

See attached for the latest gdb.out.  Note this time "this" appears to
reference valid memory.

> Thanks. Unfortunately it looks like gcc has optimised out the value for
> this. So no extra info was gained :[. You can access the correct data via
> p *(pthread_mutex *) 0xa010a58

Are you sure about the above syntax?  When I try this I get:

    (gdb) p this
    $8 = (pthread_mutex *) 0xa02b2fc
    (gdb) p *(pthread_mutex *) 0xa02b2fc
    A parse error in expression, near ` 0xa02b2fc'.

Also, the value for "this" is different when displayed by "f" and "p":

    (gdb) f 2
    #2  0x6105f34a in pthread_mutex::Lock (this=0xa010648)
    (gdb) p this
    $8 = (pthread_mutex *) 0xa02b2fc

Am I doing something wrong?

> ditto for the second trace...

Unfortunately (or fortunately), invoking python via "python" or "./python"
nows yields identical stack traces.  Additionally, two times using
"./python" did not hang.

Note that my sandbox has been modified as described by:

but otherwise, it is the same as before.


Jason Tishler
Director, Software Engineering       Phone: 732.264.8770 x235
Dot Hill Systems Corp.               Fax:   732.264.8798
82 Bethany Road, Suite 7             Email:
Hazlet, NJ 07730 USA                 WWW:

More information about the Cygwin-developers mailing list