From: Csaba Raduly <rcsaba@gmail.com>
To: simon.claude@zeusw.org, cygwin@cygwin.com
Subject: Re: Differences between C++ 'new' operator and 'malloc()' (NOT a C/C++ question)
Date: Fri, 13 Jul 2012 08:12:00 -0000 [thread overview]
Message-ID: <CAEhDDbCkeQSw5PsLm2LX_jpMHHupD3FDbDMc5Mg=n1iRezfNog@mail.gmail.com> (raw)
In-Reply-To: <4bfae5cb28706b33d48372d5a1bd80bb.squirrel@zeusw.org>
On Thu, Jul 12, 2012 at 5:59 PM, Claude SIMON wrote:
(snip)
> Since my last testings, I updated Cygwin, the JDK and the JRE. So, my
> current configuration is now :
>
> Windows Vista 32 bits SP2
> Cygwin 1.7.15
> g++ 4.5.3
> javac 1.7.0_05
> javah 1.7.0_05
> java 1.7.0_05
>
> When running the test case, I now have :
>
> $ java jcmc
> Loading library 'jcmc'...Exception in thread "main"
> java.lang.UnsatisfiedLinkError: H:\cvs\epeios\bugs\jcmc\jcmc.dll: L'accÞs
> Ó cet emplacement de la mÚmoire n'est pas valide
> at java.lang.ClassLoader$NativeLibrary.load(Native Method)
> at java.lang.ClassLoader.loadLibrary1(Unknown Source)
> at java.lang.ClassLoader.loadLibrary0(Unknown Source)
> at java.lang.ClassLoader.loadLibrary(Unknown Source)
> at java.lang.Runtime.loadLibrary0(Unknown Source)
> at java.lang.System.loadLibrary(Unknown Source)
> at jcmc.main(jcmc.java:9)
>
> There is a French message which roughly means "The access to this memory
> location is not valid"
>
> I updated the test case to reflect your changes :
> - 'Makefile' now generates the '.h' file,
> - 'Makefile' does no more contain the '--stdcall-alias' linker flag,
> - the '.cpp' contains now the `extern "C"' directive,
> - the '.h' is removed from test case, since it's now generated by the 'Makefiile'.
This sounds a bit like my JNI problem:
http://cygwin.com/ml/cygwin/2012-07/msg00043.html
Csaba
--
GCS a+ e++ d- C++ ULS$ L+$ !E- W++ P+++$ w++$ tv+ b++ DI D++ 5++
The Tao of math: The numbers you can count are not the real numbers.
Life is complex, with real and imaginary parts.
"Ok, it boots. Which means it must be bug-free and perfect. " -- Linus Torvalds
"People disagree with me. I just ignore them." -- Linus Torvalds
--
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 prev parent reply other threads:[~2012-07-13 8:12 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1342107001.13284.ezmlm@cygwin.com>
2012-07-12 16:00 ` Claude SIMON
2012-07-13 8:12 ` Csaba Raduly [this message]
2012-07-13 8:26 ` Al Slater
2012-07-13 13:03 ` Ryan Johnson
[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] <1342037244.32732.ezmlm@cygwin.com>
2012-07-12 12:12 ` Claude SIMON
2012-07-12 14:17 ` Ryan Johnson
[not found] <1341614850.23157.ezmlm@cygwin.com>
2012-07-10 16:51 ` Claude SIMON
[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='CAEhDDbCkeQSw5PsLm2LX_jpMHHupD3FDbDMc5Mg=n1iRezfNog@mail.gmail.com' \
--to=rcsaba@gmail.com \
--cc=cygwin@cygwin.com \
--cc=simon.claude@zeusw.org \
/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).