From: David Stacey <drstacey@tiscali.co.uk>
To: cygwin@cygwin.com
Subject: Re: static vs. shared linking
Date: Wed, 25 Mar 2015 22:48:00 -0000 [thread overview]
Message-ID: <551339E4.60705@tiscali.co.uk> (raw)
In-Reply-To: <20150325090453.GB3017@calimero.vinschen.de>
On 25/03/2015 09:04, Corinna Vinschen wrote:
> On Mar 24 18:39, David Stacey wrote:
>> On 24/03/2015 00:02, David Stacey wrote:
>>> I've been having difficulty building poco-1.6.0 for Cygwin for some
>>> time. I've managed to produce a test case that shows the problem:
>>>
>>> https://dl.dropboxusercontent.com/u/119453582/Cygwin/crashtest.tar.xz
>>>
>>> This archive contains source files that produce a very simple library.
>>> When linked statically, the code works fine. However, when linked as a
>>> shared DLL, the test crashes with a core dump. The behaviour is
>>> identical on x86 and x86_64 architectures.
>>>
>>> Have I made a stupid error in the compilation of the shared case, or is
>>> something more interesting going on?
>>
>> I don't know if anyone has managed to look at this. I haven't had a deluge
>> of e-mails telling me that I've done something silly (which is a shame,
>> because then I could fix it quickly and move on). For the sake of a straw to
>> clutch at, I tried compiling with clang++ rather than g++, and got the same
>> result:
>>
>> $ ./go.sh
>> Running test (static link)...
>> Done.
>>
>> Running test (shared link)...
>> ./go.sh: line 19: 3744 Aborted (core dumped)
>> ./shared_test
>> Done.
>>
>> Any help or hints would be greatly appreciated.
> For a start, you should contemplate to build your test with -g to allow
> debugging. Then you can run the testcase under GDB and get (more or less)
> useful output. The crash occurs in a delete call, afaics. If you
> install the cygwin-debuginfo package, addr2line returns something like this
> as the call stack (non-required path components removed):
>
> [...]/cygwin/exceptions.cc:1247
> [...]/cygwin/exceptions.cc:1501
> [...]/cygwin/sigproc.cc:717
> [...]/cygwin/signal.cc:252
> [...]/cygwin/signal.cc:303
> [...]/cygwin/signal.cc:313
> [...]/cygwin/signal.cc:289
> [...]/cygwin/signal.cc:375
Thank you for your comments - they were really helpful. Yes, I should
have specified '-g' on the command line - that was an omission on my
part - sorry.
I've never had much joy out of addr2line before, and I'm struggling to
recreate what you've done. I've added '-g' to the command line, run
'go.sh' again. This generates a fresh stackdump file, and then I do:
awk '/^[0-9]/{print $2}' shared_test.exe.stackdump | addr2line -f -e
shared_test.exe
but I just see question marks. Please could you show the exact lines
you're using.
Many thanks,
Dave.
--
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:[~2015-03-25 22:42 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-24 8:07 David Stacey
2015-03-24 18:50 ` David Stacey
2015-03-25 9:17 ` Corinna Vinschen
2015-03-25 17:10 ` Warren Young
2015-03-25 22:42 ` David Stacey
2015-03-25 23:28 ` David Stacey
2015-03-25 22:48 ` David Stacey [this message]
2015-03-30 11:04 ` Corinna Vinschen
2015-03-30 19:17 ` David Stacey
2015-03-30 23:02 ` Andrey Repin
2015-03-31 0:50 ` David Stacey
2015-03-31 3:26 ` Andrey Repin
2015-03-31 9:05 ` Achim Gratz
2015-03-31 10:04 ` Corinna Vinschen
2015-03-31 9:07 ` Corinna Vinschen
2015-03-31 18:00 ` David Stacey
2015-04-09 8:15 ` David Stacey
2015-04-09 17:24 ` Corinna Vinschen
2015-04-11 18:51 ` David Stacey
2015-04-09 21:32 ` Larry Hall (Cygwin)
2015-04-11 19:21 ` David Stacey
2015-03-25 23:29 ` David Stacey
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=551339E4.60705@tiscali.co.uk \
--to=drstacey@tiscali.co.uk \
--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).