This is the mail archive of the
java@gcc.gnu.org
mailing list for the Java project.
Re: c++filt causing flashing console windows
- From: Mohan Embar <gnustuff at thisiscool dot com>
- To: Tom Tromey <tromey at redhat dot com>, Andrew Haley <aph at redhat dot com>
- Cc: Ranjit Mathew <rmathew at hotmail dot com>, oyvind dot harboe at zylin dot com, java at gcc dot gnu dot org
- Date: Tue, 23 Sep 2003 13:49:02 -0500
- Subject: Re: c++filt causing flashing console windows
- Reply-to: gnustuff at thisiscool dot com
HI People,
> > Ranjit> IMHO, if the current process is a GUI application,
> > Ranjit> the spawned process (if it is a console application)
> > Ranjit> should be created with CREATE_NO_WINDOW set
> > Ranjit> in dwCreationFlags in the call to CreateProcess( ):
> >
> > Is there any reason we don't simply check this in?
>
>How?
>
>> The bit about determining whether the current process is a GUI
>> process and the to-be-spawned process is a console process is left
>> as an exercise for the reader.
For whatever it's worth, here's my internal MinGW ToDo list (written so only
I can understand it) with items in no particular order of importance.
(This doesn't mean that I want to do these myself, just that I'm interested in
seeing these get done.)
- install.texi
- check _Jv_WinStrError
- accented characters
- findCallerClass()
- console flashing
- close_on_exec()
- swt.dll, gcj.dll
- diff POSIX stuff & Win32 stuff (i.e EINTR)
- stacktraces ugly
I'm first working on getting the native compiler to work, though. :(
I'm having better luck with gdb. I suppose it helps to not set
LDFLAGS='-s' before building (slaps head with palm of hand).
-- Mohan
http://www.thisiscool.com/
http://www.animalsong.org/