From: Adam King <aking@dreammechanics.com>
To: adam@xwt.org
Cc: java@gcc.gnu.org
Subject: Re: apologies, 3.1, mingw wishlist
Date: Thu, 11 Apr 2002 10:57:00 -0000 [thread overview]
Message-ID: <20020411133628.A9444@dreammechanics.com> (raw)
In-Reply-To: <86hemkpl97.fsf@megacz.com>; from gcj@lists.megacz.com on Tue, Apr 09, 2002 at 03:20:20PM -0700
On Tue, Apr 09, 2002 at 03:20:20PM -0700, Adam Megacz wrote:
>
> First off, sorry I've been neglecting gcj recently.
Don't be - you did a great job supporting the mingw32 target!
Getting our 200k+ lines of java code to work with it is progressing
much better than I expected. So far, I've only come across three
places where we use an API method not supported by gcj.
If you're taking votes...
> - Make Win32Process work
Yes please! We use it in a couple of places, and if you don't
add it, I'll have to in a couple of weeks. Also, if you want to
add in Runtime.exec( String[], String[], File ) (added in 1.3 I think )
that would be great.
> And, if I have time:
>
> - Stack traces
This would be _very_ useful - while getting our code to compile, an
exception would be thrown but I didn't know from where. I'd end up
having to stick a bunch of printlns throughout the code to track
down its cause.
> Is there anything else that I should consider?
Is there any way that GDB would/could be used for debugging?
Anyways, thanks again for your work on the port ( and also, to
all the gcj coders! !
Adam K
next prev parent reply other threads:[~2002-04-11 17:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-09 15:29 Adam Megacz
2002-04-09 15:36 ` Tom Tromey
2002-04-09 17:50 ` Brian Jones
2002-04-11 10:57 ` Adam King [this message]
2002-04-11 12:52 ` apologies, 3.1, mingw wishlist [okay to add new ctor to ConcreteProcess?] Adam Megacz
2002-04-11 15:20 ` Tom Tromey
2002-04-11 15:53 ` Java debugger Adam King
2002-04-11 17:28 ` Nic Ferrier
2002-04-11 17:36 ` Bryce McKinlay
2002-04-11 23:13 ` apologies, 3.1, mingw wishlist [okay to add new ctor to ConcreteProcess?] Adam Megacz
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=20020411133628.A9444@dreammechanics.com \
--to=aking@dreammechanics.com \
--cc=adam@xwt.org \
--cc=java@gcc.gnu.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).