From: "Parker, Ron" <rdparker@butlermfg.com>
To: "'cygwin@sourceware.cygnus.com'" <cygwin@sourceware.cygnus.com>
Cc: Carl Thompson <cet@carlthompson.net>
Subject: RE: problems with latest Cygwin 1.1
Date: Mon, 05 Jun 2000 10:52:00 -0000 [thread overview]
Message-ID: <20028.960227564.0@NO-ID-FOUND.mhonarc.org> (raw)
> -----Original Message-----
> From: Carl Thompson [ mailto:cet@carlthompson.net ]
> Sent: Monday, June 05, 2000 12:43 AM
> To: cygwin@sourceware.cygnus.com
> Subject: problems with latest Cygwin 1.1
>
>
> Hello,
>
> I'm having problems using the latest Cygwin release
> (just downloaded
> and installed today using today's setup.exe). If I compile
> any trivial C++
> application with the "-mno-cygwin" option, the compile
> apparently succeeds
> but when the application is run it faults. I am running on
> Windows 2000.
> Using the C compiler to generate executables works fine; just
> executables
> compiled using the C++ compiler die. I have used older
> versions (1.0) of
> Cygwin with success. My development project (the LGPLed FLTK
> cross platform
> GUI toolkit) does not require the Cygwin DLL, however it does
> require the
> Cygwin build enviroment.
>
> Also, the Insight debugger supplied with the latest
> Cygwin cannot seem
> to find / process source files on my system. When I start up
> the debugger
> with an executable compiled with the "-g" flag, it pops up a
> dialog with a
> lot of error output apparently related to loading the source
> file. The
> program's source is not displayed, nor does it seem to know the source
> files' names as normal. I've used a previous version on a
> previous version
> of Cygwin with success.
>
> Are the bugs known and is it known when they will be
> fixed? I would
> rather not go back to 1.0 because I have to heavily modify it
> to use newer
> compilers and tools (takes a while).
>
> Please CC me in any responses; I am not on the list.
I might suggest that you go to the mailing list archives and do a search.
Both of these topics have been abused to death on the list in the last
month. See http://sourceware.cygnus.com/ml/cygwin/ and
http://www.delorie.com/archives/ for two different archive interfaces.
This thread addresses what might be causing your 'fault'.
http://www.delorie.com/archives/search.cgi?search=Exception+Handling+Broken& ;
since=month&db=cygwin
And a search for 'gdb' will yeild enough reading material for the next
month.
HTH
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
next reply other threads:[~2000-06-05 10:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-06-05 10:52 Parker, Ron [this message]
[not found] <20000606170446.97480803A@carlthompson.net>
2000-06-06 11:48 ` Carl Thompson
-- strict thread matches above, loose matches on Subject: below --
2000-06-06 10:00 Parker, Ron
[not found] <20000605223940.20829803A@carlthompson.net>
2000-06-05 18:20 ` Carl Thompson
2000-06-05 18:37 ` Chris Faylor
2000-06-05 18:42 ` Carl Thompson
2000-06-05 15:35 Parker, Ron
[not found] <20000605175626.9DCBC803A@carlthompson.net>
2000-06-05 14:57 ` Carl Thompson
2000-06-04 22:37 Carl Thompson
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=20028.960227564.0@NO-ID-FOUND.mhonarc.org \
--to=rdparker@butlermfg.com \
--cc=cet@carlthompson.net \
--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).