public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Thomas D. Dean" <tomdean@speakeasy.org>
To: cygwin@cygwin.com
Subject: Re: 1.7.9: static const std::string initialization lost in child process when using fork, dlopen
Date: Sun, 21 Aug 2011 23:56:00 -0000	[thread overview]
Message-ID: <1313970991.31093.46.camel@asus> (raw)
In-Reply-To: <20110821221923.GA30284@ednor.casa.cgf.cx>

On Sun, 2011-08-21 at 18:19 -0400, Christopher Faylor wrote:
> 're reporting.
> 
> If you don't want to try a snapshot for some reason then you could also
> try setting the base address of the DLL by using the --auto-image-base
> option when linking the DLL.

I used 

g++ -Wall -I. -shared -g -c dll.cpp -o dll.o
g++ -Wall -shared -o libdll.dll dll.o
g++ -Wall -I. -g -c dlltest.cpp -o dlltest.o
g++ -Wall -o dlltest dlltest.o -L. -ldll -Wl,--enable-auto-image-base

I still have the stackdump problem.

I used hd to look at the files I created with emacs and there are no
strange characters.

tomdean


--
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

  parent reply	other threads:[~2011-08-21 23:56 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-21 11:48 whans
2011-08-21 16:50 ` Christopher Faylor
2011-08-21 17:10   ` Cliff Hones
2011-08-21 18:39     ` Christopher Faylor
2011-08-21 21:15       ` Thomas D. Dean
2011-08-21 22:19         ` Christopher Faylor
2011-08-21 23:15           ` Thomas D. Dean
2011-08-21 23:56           ` Thomas D. Dean [this message]
2011-08-22  1:44             ` Christopher Faylor
2011-08-22  3:57               ` Thomas D. Dean
2011-08-22  5:11                 ` Christopher Faylor
2011-08-22  5:52                   ` Thomas D. Dean
2011-08-21 17:05 ` Christopher Faylor

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=1313970991.31093.46.camel@asus \
    --to=tomdean@speakeasy.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).