From: "Robert McNulty Junior" <sherlock_abc@netzero.net>
To: "Remi Lejeune" <Remi.Lejeune@lhs.be>, <cygwin@sourceware.cygnus.com>
Cc: "Frederik Durant" <Frederik.Durant@lhs.be>,
"Remi Lejeune" <Remi.Lejeune@lhs.be>
Subject: Re: VirtualAlloc failed from DOS Prompt
Date: Mon, 20 Mar 2000 02:59:00 -0000 [thread overview]
Message-ID: <000801bf925b$452cb3e0$8c763004@default> (raw)
>I have a program, blablabla.cpp, which compiles (gnu g++) and runs
successfully
> on various platforms, including windows NT/ cygnus provided bash shell.
>Though, when I try to run the VERY SAME executable calling it from a DOS
prompt
>(whith cygwin1.dll in the same directory),
>I get the following error messages :
>
>[main] C:\Remi\backbone\scripts\PPlmTools\bin\debug\blablabla.exe 1535 (0)
>commit_and_inc: VirtualAlloc failed
>bla bouh
>[main] prunebigrams 1535 (0) handle_exceptions: Exception:
>STATUS_ACCESS_VIOLATION
>[main] prunebigrams 1535 (0) handle_exceptions: Dumping stack trace to
>blablabla.exe.core
>
>What I dont understand is how come this program runs on the bash shell and
>crashes when called from the DOS prompt, with the same parameters of
course.
>
>Any idea ?
>
>Remi@completely.stuck
>
>
>
>--
>Want to unsubscribe from this list?
>Send a message to cygwin-unsubscribe@sourceware.cygnus.com
>
Try placing Cygwin1.dll in the windows directory.
__________________________________________
NetZero - Defenders of the Free World
Get your FREE Internet Access and Email at
http://www.netzero.net/download/index.html
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
next reply other threads:[~2000-03-20 2:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-03-20 2:59 Robert McNulty Junior [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-03-20 6:18 Earnie Boyd
2000-03-20 2:48 Remi Lejeune
2000-03-20 8:12 ` Chris Faylor
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='000801bf925b$452cb3e0$8c763004@default' \
--to=sherlock_abc@netzero.net \
--cc=Frederik.Durant@lhs.be \
--cc=Remi.Lejeune@lhs.be \
--cc=cygwin@sourceware.cygnus.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).