Re: 1.7.9: static const std::string initialization lost in child process when using fork, dlopen

2011-08-21 Thread Thomas D. Dean
Thanks, I just built a DLL I am interested in - it works. 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

Re: 1.7.9: static const std::string initialization lost in child process when using fork, dlopen

2011-08-21 Thread Thomas D. Dean
On Sun, 2011-08-21 at 21:44 -0400, Christopher Faylor wrote: > On Sun, Aug 21, 2011 at 04:56:31PM -0700, Thomas D. Dean wrote: > >On Sun, 2011-08-21 at 18:19 -0400, Christopher Faylor wrote: > >> 're reporting. > >> > >> If you don't want to try

Re: 1.7.9: static const std::string initialization lost in child process when using fork, dlopen

2011-08-21 Thread Thomas D. Dean
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 dl

Re: 1.7.9: static const std::string initialization lost in child process when using fork, dlopen

2011-08-21 Thread Thomas D. Dean
On Sun, 2011-08-21 at 18:19 -0400, Christopher Faylor wrote: > On Sun, Aug 21, 2011 at 02:15:16PM -0700, Thomas D. Dean wrote: > >On Sun, 2011-08-21 at 14:38 -0400, Christopher Faylor wrote: > > > >I get the stack dump - I retyped the examples to be sure no strange > >

Re: 1.7.9: static const std::string initialization lost in child process when using fork, dlopen

2011-08-21 Thread Thomas D. Dean
On Sun, 2011-08-21 at 14:38 -0400, Christopher Faylor wrote: I get the stack dump - I retyped the examples to be sure no strange chars. And, I see no strange characters in the emails - evolution Ubuntu 10.04 tomdean -- Problem reports: http://cygwin.com/problems.html FAQ:

Re: x86_64-w64-ming32-g++ file not recognized by objdump

2011-08-20 Thread Thomas D. Dean
On Sun, 2011-08-21 at 11:32 +0800, JonY wrote: > you are probably missing the runtime DLLs from path. They should be > found in "/usr/x86_64-w64-mingw32/sys-root/mingw/bin". > > You are correct. export PATH="$PATH:/usr/x86_64-w64-mingw32/sys-root/mingw/bin" fixed the problem. Thanks tomdean

Re: x86_64-w64-ming32-g++ file not recognized by objdump

2011-08-20 Thread Thomas D. Dean
On Sun, 2011-08-21 at 11:32 +0800, JonY wrote: > Hi Thomas, > > you are probably missing the runtime DLLs from path. They should be > found in "/usr/x86_64-w64-mingw32/sys-root/mingw/bin". > > I have: libgcc_s_sjlj-1.dll libgfortran-3.dll libgomp-1.dll libobjc-2.dll libssp-0.dll libstdc++-6.dl

Re: x86_64-w64-ming32-g++ file not recognized by objdump

2011-08-20 Thread Thomas D. Dean
? > - Original Message - > From: "Thomas D. Dean" > > > #include > > #include > > using namespace std; > > int main() { > > vector vs; > > vs.push_back("asdf"); > > } > > > > > > If I compile with x

x86_64-w64-ming32-g++ file not recognized by objdump

2011-08-20 Thread Thomas D. Dean
I am missing something, I think. I have a simple application, taken from the web, t.cc #include #include using namespace std; int main() { vector vs; vs.push_back("asdf"); } If I compile with g++, I get an executable that works, i.e. runs without error. This file is recognized by

x86_64-w64-ming32-g++ file not recognized by objdump

2011-08-20 Thread Thomas D. Dean
I am missing something, I think. I have a simple application, taken from the web, t.cc #include #include using namespace std; int main() { vector vs; vs.push_back("asdf"); } If I compile with g++, I get an executable that works, i.e. runs without error. This file is recognized by