public inbox for rhug-rhats@sourceware.org
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: Christophe Roux <ch_roux@club-internet.fr>
Cc: rhug-rhats@sources.redhat.com
Subject: Re: debugging
Date: Tue, 17 Sep 2002 16:32:00 -0000	[thread overview]
Message-ID: <87wupkmbx3.fsf@fleche.redhat.com> (raw)
In-Reply-To: <E17qz4j-0000pB-00@smarthost1.mail.easynet.fr>

>>>>> "Christophe" == Christophe Roux <ch_roux@club-internet.fr> writes:

Christophe> So I want to use server side gdb in order to track my bugs.
Christophe> Can someone tell me how to use gdb with rhug-tomcat?

I've never tried it.  However, a general technique that might work is
to attach to the running gcj-compiled process using gdb.  See the
`attach' command.  Doing this effectively may involve adding sleep()
calls to your program... not to mention working around areas where
gdb's gcj support is less than ideal.

Tom

  reply	other threads:[~2002-09-17 23:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-16  9:50 debugging Christophe Roux
2002-09-17 16:32 ` Tom Tromey [this message]
2002-09-18 10:15 debugging Christophe Roux

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=87wupkmbx3.fsf@fleche.redhat.com \
    --to=tromey@redhat.com \
    --cc=ch_roux@club-internet.fr \
    --cc=rhug-rhats@sources.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).