public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Daniel Colascione <dancol@dancol.org>
To: cygwin@cygwin.com
Subject: Re: python aborts
Date: Thu, 25 Jul 2013 08:28:00 -0000	[thread overview]
Message-ID: <51F0CBD2.2030502@dancol.org> (raw)
In-Reply-To: <20130522123148.GW2406@calimero.vinschen.de>

[-- Attachment #1: Type: text/plain, Size: 2069 bytes --]

I just started seeing this problem myself --- on 1.7.22 release.

On 5/22/2013 5:31 AM, Corinna Vinschen wrote:
> On May 22 11:11, Denis Excoffier wrote:
>> Hello,
>>
>> With the current snapshot (20130521) on Windows XP, the following
>> fails (with an empty stackdump):
>>
>> % /usr/bin/python pyfoo
>> Abort (core dumped)
>> % cat pyfoo
>> import xml.sax
>> xml.sax.make_parser()
>> % cat python2.7.exe.stackdump
>> Stack trace:
>> Frame     Function  Args
>> % /usr/bin/python --version
>> Python 2.7.3
>> %
>>
>> With some dichotomy, i found that under the 20130430 snapshot it works
>> (no "abort", no stackdump), but under 20130501 it does the same
>> as today (ie abort).
> 
> I have another effect.  In my case the 20130430 snapshot does not
> print the "Abort (core dumped)" message, but it still creates the
> more or less empty stackdump file as above.  So, AFAICS, the crash
> occured before, only you didn't see it.  With Cygwin 1.7.17,
> I only get an "Abort" and an entirely empty stackdump.

I can run python -c 'import _wp,sqlite3' and see Python abort, but if I swap the
module order, everything seems to be fine. gdb is useless if I wait until it
breaks, but if i set a breakpoint on cygwin1!abort beforehand, I get this stack:

(gdb) where
#0  abort () at /usr/src/debug/cygwin-1.7.22-1/winsup/cygwin/signal.cc:362
#1  0xc3b05111 in cyggcc_s-1!__deregister_frame_info_bases () from
/usr/bin/cyggcc_s-1.dll
#2  0x65fc10e2 in __gcc_deregister_frame () from C:/users/dancol/wptools/_wp.dll
#3  0x610265f5 in run_dtors (this=<optimized out>)
    at /usr/src/debug/cygwin-1.7.22-1/winsup/cygwin/dll_init.cc:80
#4  run_dtors (this=<optimized out>) at
/usr/src/debug/cygwin-1.7.22-1/winsup/cygwin/dll_init.h:72
#5  run_dtors (this=<optimized out>) at
/usr/src/debug/cygwin-1.7.22-1/winsup/cygwin/dll_init.cc:41
#6  dll_global_dtors () at
/usr/src/debug/cygwin-1.7.22-1/winsup/cygwin/dll_init.cc:52

Does that help at all?  I only started seeing this problem after I recompiled
_wp.dll using gcc 4.7.3.


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 260 bytes --]

  reply	other threads:[~2013-07-25  6:55 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-22  9:11 Denis Excoffier
2013-05-22 12:31 ` Corinna Vinschen
2013-07-25  8:28   ` Daniel Colascione [this message]
2013-07-25  8:36     ` Daniel Colascione
2013-07-25 10:18       ` Daniel Colascione
2013-07-25 10:54         ` Corinna Vinschen
2013-07-25 12:12           ` JonY
2013-07-25 13:02             ` JonY
2013-07-25 15:36               ` Christopher Faylor
2013-07-25 17:20                 ` JonY
2013-07-25 17:47                   ` Christopher Faylor
2013-07-25 22:36                     ` JonY
2013-07-26  4:14                       ` Christopher Faylor
2013-08-28  3:59                         ` Christopher Faylor
2013-11-06 22:30                           ` Jean-Pierre Flori
2013-11-07 13:20                             ` Corinna Vinschen
2013-11-07 21:55                               ` Jean-Pierre Flori
2013-11-08 16:40                               ` Jean-Pierre Flori
2013-11-11 12:59                               ` Corinna Vinschen
2013-11-11 13:02                                 ` JonY
2013-11-11 13:08                                   ` Corinna Vinschen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=51F0CBD2.2030502@dancol.org \
    --to=dancol@dancol.org \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).