[Mingw-w64-public] Problems in retrieving stack backtrace in the case of c++ exceptions

2014-04-24 Thread lh_mouse
Dear all, I copied some code from here http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33903#c5 and removed those dl* stuffs and tested it. But this piece of code only works on my linux. I got this result with mingw-w64-gcc x86 version: E:\Desktop>g++ -v Thread model: win32 gcc version 4

Re: [Mingw-w64-public] [patch/cygwin]: Fix u_long problem on LP64 systems

2014-04-24 Thread Corinna Vinschen
On Apr 24 15:55, Kai Tietz wrote: > Hello Corinna, > > good catch. Patch is ok. Please apply. Done. Thanks, Corinna pgpRE_5zsASTC.pgp Description: PGP signature -- Start Your Social Network Today - Download eXo Platf

Re: [Mingw-w64-public] [patch/cygwin]: Fix u_long problem on LP64 systems

2014-04-24 Thread Kai Tietz
Hello Corinna, good catch. Patch is ok. Please apply. Thanks, Kai 2014-04-24 15:13 GMT+02:00 Corinna Vinschen : > Hi, > > > I just stumbled over a weird problem in Cygwin's socket code, which I > tracked down to a wrong definition of struct sockaddr_in6. It had the > correct size (28 bytes) in

[Mingw-w64-public] [patch/cygwin]: Fix u_long problem on LP64 systems

2014-04-24 Thread Corinna Vinschen
Hi, I just stumbled over a weird problem in Cygwin's socket code, which I tracked down to a wrong definition of struct sockaddr_in6. It had the correct size (28 bytes) in the application but it was supposedly 40 bytes in the Cygwin DLL. I tracked it down to the fact that the re-definition of u_

Re: [Mingw-w64-public] Experimental builds of GCC-4.9.0

2014-04-24 Thread Alexpux
24 апр. 2014 г., в 14:19, Koehne Kai написал(а): >> -Original Message- >> From: niXman [mailto:i.nix...@autistici.org] >> Sent: Tuesday, November 19, 2013 10:10 PM >> To: mingw-w64-public >> Subject: [Mingw-w64-public] Experimental builds of GCC-4.9.0 >> >> >> Hi guys! >> Just now I up

Re: [Mingw-w64-public] Experimental builds of GCC-4.9.0

2014-04-24 Thread Koehne Kai
> -Original Message- > From: niXman [mailto:i.nix...@autistici.org] > Sent: Tuesday, November 19, 2013 10:10 PM > To: mingw-w64-public > Subject: [Mingw-w64-public] Experimental builds of GCC-4.9.0 > > > Hi guys! > Just now I uploaded new builds based on the GCC-4.9.0-trunk(rev. > 205009)

Re: [Mingw-w64-public] mingw intrinsics header clashes with clang intrinsics

2014-04-24 Thread Ruben Van Boxem
2014-04-24 11:45 GMT+02:00 Jacek Caban : > On 04/24/14 11:26, G M wrote: > > Hi Everyone > > > > I thought you might want to know that if I use clang 3.5 from trunk to > > compile mingw's windows.h file like so: > > > > // w3.cpp - no main even > > #include > > clang++ -fms-extensions w3.cpp > >

Re: [Mingw-w64-public] mingw intrinsics header clashes with clang intrinsics

2014-04-24 Thread Jacek Caban
On 04/24/14 11:26, G M wrote: > Hi Everyone > > I thought you might want to know that if I use clang 3.5 from trunk to > compile mingw's windows.h file like so: > > // w3.cpp - no main even > #include > clang++ -fms-extensions w3.cpp > > I get errors the errors shown below. I emailed one of the gu

[Mingw-w64-public] mingw intrinsics header clashes with clang intrinsics

2014-04-24 Thread G M
Hi Everyone I thought you might want to know that if I use clang 3.5 from trunk to compile mingw's windows.h file like so: // w3.cpp - no main even #include clang++ -fms-extensions w3.cpp I get errors the errors shown below. I emailed one of the guys on the clang team to ask what they thought w