From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: static vs. shared linking
Date: Tue, 31 Mar 2015 09:07:00 -0000 [thread overview]
Message-ID: <20150331090527.GB32403@calimero.vinschen.de> (raw)
In-Reply-To: <5519A0E1.6020707@tiscali.co.uk>
[-- Attachment #1: Type: text/plain, Size: 1654 bytes --]
On Mar 30 20:15, David Stacey wrote:
> On 30/03/15 11:55, Corinna Vinschen wrote:
> >On Mar 25 22:42, David Stacey wrote:
> >>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.
> >addr2line is a bit dumb and needs help. What I do is to cat the
> >stackdump file and look at the addresses. They usually show where
> >the stuff comes from:
> >[...]
>
> Thank you for your reply and the explanation. That requires quite a bit of
> knowledge before addr2line is usable - no wonder I've never had anything
> sensible out of it before!
>
> Back to the matter in hand - I don't suppose you had thoughts on why my
> simple application crashes when linked as shared, but works fine when linked
> statically?
No, sorry. This may be a c++11 thingy which requires "something" in
libstdc++ and Cygwin, but I don't know what that could be. It's
especially weird that free() aborts. This points to some malloc/free
inconsistency, as if the malloc (or new) call used another
implementation of malloc than the aborting free call. It may also
be a memory overflow issue but that would show up on other platforms
as well.
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Maintainer cygwin AT cygwin DOT com
Red Hat
[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-03-31 9:05 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
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 [this message]
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=20150331090527.GB32403@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.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).