From: jojelino <jojelino@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Built perl 5.6.2 on Cygwin 1.7.11, but get SIGABRT from resulting perl.exe
Date: Wed, 18 Jul 2012 02:51:00 -0000 [thread overview]
Message-ID: <ju58bb$dbp$1@dough.gmane.org> (raw)
In-Reply-To: <A6DBD2A0155D5F468DAC4364F671A6C2048D6C4E@CH1PRD0711MB406.namprd07.prod.outlook.com>
On 2012-07-18 AM 4:55, Nicholas DiPiazza wrote:
> Jojelino asked:
>
> "and then, what was the result of
> gdb --args perl
> b _sigfe_free if *((unsigned*)$esp+1)==0x20000010 #which i am interested in to see what the backtrace was.
> disp *((unsigned*)$esp+1)
> r
> bt #when breakpoint is hit"
>
>
> Here is the result:
>
> $ gdb --args perl
> GNU gdb (GDB) 7.3.50.20111026-cvs (cygwin-special)
> Copyright (C) 2011 Free Software Foundation, Inc.
> License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
> This is free software: you are free to change and redistribute it.
> There is NO WARRANTY, to the extent permitted by law. Type "show copying"
> and "show warranty" for details.
> This GDB was configured as "i686-cygwin".
> For bug reporting instructions, please see:
> <http://www.gnu.org/software/gdb/bugs/>...
> Reading symbols from /home/windows7-vm/perl-5.6.2/perl...done.
> (gdb) b _sigfe_free if *((unsigned*)$esp+1)==0x20000010
> Function "_sigfe_free" not defined.
> Make breakpoint pending on future shared library load? (y or [n]) y
>
> Breakpoint 1 (_sigfe_free if *((unsigned*)$esp+1)==0x20000010) pending.
> (gdb) disp *((unsigned*)$esp+1)
> (gdb) r
> Starting program: /home/windows7-vm/perl-5.6.2/perl
> [New Thread 2320.0xc08]
> [New Thread 2320.0xdac]
>
> Program received signal SIGABRT, Aborted.
> 0x7718f8b1 in ntdll!RtlUpdateClonedSRWLock ()
> from /cygdrive/c/Windows/system32/ntdll.dll
> 1: *((unsigned*)$esp+1) = 1987840657
> (gdb) bt
> #0 0x7718f8b1 in ntdll!RtlUpdateClonedSRWLock ()
> from /cygdrive/c/Windows/system32/ntdll.dll
> #1 0x7718f8b1 in ntdll!RtlUpdateClonedSRWLock ()
> from /cygdrive/c/Windows/system32/ntdll.dll
> #2 0x767c0a91 in WaitForSingleObjectEx ()
> from /cygdrive/c/Windows/syswow64/KERNELBASE.dll
> #3 0x000000a8 in ?? ()
> #4 0x00000000 in ?? ()
>
>
I'm sorry, the breakpoint wasn't hit. what was the result of
gdb --args perl
symbol cygwin1.dll
define btc
bt
c
end
# "Function "_sigfe_free" not defined." shouldn't be seen. if it does,
please use latest snapshot including debug symbol.
b _sigfe_free
disp *((unsigned*)$esp+1)
r
btc
#and just press enter until sigabrt is hit.
--
Regards.
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2012-07-18 2:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-17 19:56 Nicholas DiPiazza
2012-07-18 2:51 ` jojelino [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-07-18 17:46 Nicholas DiPiazza
2012-07-19 2:01 ` jojelino
2012-07-16 19:53 Nicholas DiPiazza
2012-07-17 3:25 ` jojelino
[not found] <014d01cd4fd5$0125df60$03719e20$@gmail.com>
2012-06-21 17:46 ` Nicholas DiPiazza
2012-06-23 15:25 ` Reini Urban
[not found] ` <010701cd637e$d3693910$7a3bab30$@gmail.com>
[not found] ` <011301cd637f$62ebf640$28c3e2c0$@gmail.com>
2012-07-16 18:35 ` Nicholas DiPiazza
2012-07-16 19:01 ` jojelino
2012-07-16 19:30 ` Nicholas DiPiazza
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='ju58bb$dbp$1@dough.gmane.org' \
--to=jojelino@gmail.com \
--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).