From: Nic Ferrier <nferrier@tapsellferrier.co.uk>
To: Adam King <aking@dreammechanics.com>
Cc: Tom Tromey <tromey@redhat.com>, java@gcc.gnu.org
Subject: Re: Java debugger
Date: Thu, 11 Apr 2002 17:28:00 -0000 [thread overview]
Message-ID: <87y9ftdf2v.fsf@pooh-sticks-bridge.tapsellferrier.co.uk> (raw)
In-Reply-To: <20020411183648.D9444@dreammechanics.com>
Adam King <aking@dreammechanics.com> writes:
> On Thu, Apr 11, 2002 at 03:28:37PM -0600, Tom Tromey wrote:
> >
> > Adam M> Hrm, I already use cygwin's GDB. It's not the best -- if your
> > Adam M> code CALL's a NULL address you lose the stack, and the GUI is a
> > Adam M> bit lacking -- but it's better than nothing.
> >
> > The current gdb's gcj support isn't all that great.
> > Even worse, nobody is working on it :-(
>
> hmm.. I currently use JSwat for most of my current java debugging
> needs - so I was wondering, is anyone working on a JPDA
> implementation? Would it even be possible since it's something
> I wouldn't mind giving a try adding to gcj.
GDB is the debugger of choice for gcj hackers. It's a shame that GCJ
still can't debug byte codes because compiling lots of code to native
code can be a pain.
Nic
next prev parent reply other threads:[~2002-04-11 22:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-09 15:29 apologies, 3.1, mingw wishlist Adam Megacz
2002-04-09 15:36 ` Tom Tromey
2002-04-09 17:50 ` Brian Jones
2002-04-11 10:57 ` Adam King
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 [this message]
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=87y9ftdf2v.fsf@pooh-sticks-bridge.tapsellferrier.co.uk \
--to=nferrier@tapsellferrier.co.uk \
--cc=aking@dreammechanics.com \
--cc=java@gcc.gnu.org \
--cc=tromey@redhat.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).