delorie.com/archives/browse.cgi | search |
X-Recipient: | archive-cygwin AT delorie DOT com |
X-SWARE-Spam-Status: | No, hits=-4.8 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,KHOP_RCVD_TRUST,KHOP_THREADED,RCVD_IN_DNSWL_LOW,RCVD_IN_HOSTKARMA_YE |
X-Spam-Check-By: | sourceware.org |
MIME-Version: | 1.0 |
In-Reply-To: | <ce08d44ac1c41b2145456992672dbc20.squirrel@zeusw.org> |
References: | <1341437446 DOT 12368 DOT ezmlm AT cygwin DOT com> <ce08d44ac1c41b2145456992672dbc20 DOT squirrel AT zeusw DOT org> |
Date: | Fri, 6 Jul 2012 07:47:54 -0400 |
Message-ID: | <CAF1jjLuPV+nYP7uOa8_AAa9b1dkLTruwq=a-K7oZN2=RkRHtCA@mail.gmail.com> |
Subject: | Re: Differences between C++ 'new' operator and 'malloc()' (NOT a C/C++ question) |
From: | NightStrike <nightstrike AT gmail DOT com> |
To: | sc DOT cygwin DOT com AT zeusw DOT org, cygwin AT cygwin DOT com |
X-IsSubscribed: | yes |
Mailing-List: | contact cygwin-help AT cygwin DOT com; run by ezmlm |
List-Id: | <cygwin.cygwin.com> |
List-Unsubscribe: | <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com> |
List-Subscribe: | <mailto:cygwin-subscribe AT cygwin DOT com> |
List-Archive: | <http://sourceware.org/ml/cygwin/> |
List-Post: | <mailto:cygwin AT cygwin DOT com> |
List-Help: | <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs> |
Sender: | cygwin-owner AT cygwin DOT com |
Mail-Followup-To: | cygwin AT cygwin DOT com |
Delivered-To: | mailing list cygwin AT cygwin DOT com |
On Thu, Jul 5, 2012 at 9:36 AM, Claude SIMON <sc DOT cygwin DOT com AT zeusw DOT org> wrote: > Let's consider a Java native component which only calls a 'malloc(1)'. It > doesn't even test the returned value (it is usually not a good idea, but > it doesn't matter here). > > This component : > - compiled with g++ under Linux : works, > - compiled with g++ under Mac OS : works, > - compiled with Visual C++ under Windows : works, > - compiled with g++ under Cygwin : CRASHES ! > > It crashes as soon the 'malloc(1)' function is called. You don't even have > the opportunity to test the returned value, nor to use it. It's perhaps a > Cygwin bug, or perhaps a JVM/JRE/JDK bug ; I don't know and I don't bother > (but if someone will make some investigation about that, I'm ready to help > him or her if I can). > > When you replace the 'malloc()' by the 'new' operator, then the component > compiled with g++ under Cygwin works too. Can you provide a reduced self contained small test case that demonstrates the problem? That'll be your fastest path to a resolution. It's also the easiest way to explain what you are seeing. -- 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
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |