From: "Claude SIMON" <sc.cygwin.com@zeusw.org>
To: cygwin@cygwin.com
Subject: Re: Differences between C++ 'new' operator and 'malloc()' (NOT a C/C++ question)
Date: Tue, 10 Jul 2012 16:51:00 -0000 [thread overview]
Message-ID: <f04272a0af1767f921ed51727a081a19.squirrel@zeusw.org> (raw)
In-Reply-To: <1341614850.23157.ezmlm@cygwin.com>
NightStrike wrote:
> On Thu, Jul 5, 2012 at 9:36 AM, Claude SIMON <sc.cygwin.com@zeusw.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.
>
Thanks for your interest.
I've made a test case which can be found at :
http://cvs.savannah.gnu.org/viewvc/epeios/bugs/jcmc/?root=epeios
There is a 'README' file with further explanations.
--
Claude SIMON (sc.cygwin.com@zeusw.org)
--
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
next parent reply other threads:[~2012-07-10 16:51 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1341614850.23157.ezmlm@cygwin.com>
2012-07-10 16:51 ` Claude SIMON [this message]
[not found] <1342195424.30517.ezmlm@cygwin.com>
2012-07-18 8:03 ` Claude SIMON
2012-07-18 8:21 ` Claude SIMON
2012-07-18 8:42 ` Claude SIMON
2012-07-18 9:27 ` Eliot Moss
2012-07-18 10:23 ` Yaakov (Cygwin/X)
[not found] <1342107001.13284.ezmlm@cygwin.com>
2012-07-12 16:00 ` Claude SIMON
2012-07-13 8:12 ` Csaba Raduly
2012-07-13 8:26 ` Al Slater
2012-07-13 13:03 ` Ryan Johnson
[not found] <1342037244.32732.ezmlm@cygwin.com>
2012-07-12 12:12 ` Claude SIMON
2012-07-12 14:17 ` Ryan Johnson
[not found] <1341539419.17571.ezmlm@cygwin.com>
2012-07-10 16:46 ` Claude SIMON
2012-07-11 19:47 ` Ryan Johnson
[not found] <1341437446.12368.ezmlm@cygwin.com>
2012-07-05 13:37 ` Claude SIMON
2012-07-05 20:05 ` Ryan Johnson
2012-07-06 11:48 ` NightStrike
2012-07-04 9:45 Claude SIMON
2012-07-04 13:48 ` Ryan Johnson
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=f04272a0af1767f921ed51727a081a19.squirrel@zeusw.org \
--to=sc.cygwin.com@zeusw.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).