From: fieldhouse@logica.com (Dirk Fieldhouse)
To: cygwin@sourceware.cygnus.com
Subject: RE: -mno-cygwin: STATUS_STACK_OVERFLOW before main
Date: Wed, 02 Feb 2000 11:04:00 -0000 [thread overview]
Message-ID: <200002021904.TAA22520@cav.logica.co.uk> (raw)
On Tue, 01 Feb 2000 12:47:52 -0300, salvador <salvador at inti dot gov dot ar> wrote:
> I have an application that compiles fine using Mingw32. When I
> try to compile it using Cygwin B20.1 (adding -mno-cygwin and
> -lmingw32 -lcrtdll) I get an executable, but it dies before
> reaching main with an STATUS_STACK_OVERFLOW error.
>
> I tried with --stack XXXX without luck (same crash in same
> place).
>...
Check your include and link paths. Your supposed mingw32 app is obviously not one.
A cygwin installation can easily get confused about a mingw32 target because some #define or library reference may be accidentally resolved against the cygwin include/library files which may follow the mingw32 ones in the search paths. This is almost certainly the problem here. Is your program C++ or C - I have seen this with C++ in the past ?
There is some confusion (for me at least) about which files are usable in both targets - those for the Windows OS (.h and lib*.a) ought to be OK.
I guess the appropriate resolution of this is for the -mno-cygwin specs to select a different set of paths and use -nostdinc (and the ld equivalent) or similar to avoid picking up cygwin stuff from well-known locations like /usr/include - or to be sure that you don't put cygwin stuff in any of these places.
--
Dirk Fieldhouse Logica UK Limited
fieldhouse@logica.com 75 Hampstead Road
c=gb;a=attmail;p=logica; London NW1 2PL
o=LOGICA;ou1=UK;s=fieldhouse UK
+44 (20) 7637 9111
- not speaking for Logica
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
next reply other threads:[~2000-02-02 11:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-02-02 11:04 Dirk Fieldhouse [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-02-03 9:53 Earnie Boyd
2000-02-03 10:31 ` salvador
2000-02-03 9:18 salvador
2000-02-01 7:41 salvador
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=200002021904.TAA22520@cav.logica.co.uk \
--to=fieldhouse@logica.com \
--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).