Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Johan Walles <johan.walles@appeal.se>
To: gdb@sources.redhat.com
Subject: Trouble debugging a Java Virtual Machine on Linux
Date: Thu, 24 Jan 2002 05:23:00 -0000	[thread overview]
Message-ID: <3C500AAC.5030709@appeal.se> (raw)

Hi!

We are having trouble debugging our Java Virtual Machine on Linux.  The 
reason is that:

JRockit (our virtual machine) uses ptrace() for controlling threads. 
Gdb uses ptrace() for controlling processes / threads.  Linux does not 
allow two processes (like both gdb and JRockit) at a time to ptrace() 
one target process (in our case, a Java thread).

Thus, as both gdb and JRockit tries to PTRACE_ATTACH, they clash.

We have discussed a number of solutions to this problem, and we are 
currently leaning towards making some sort of (non-JRockit specific) 
modifications to gdb so that a debuggee can provide alternative ways for 
gdb to manage processes.

Now, I'd like very much to get some input from somebody knowledgable 
about gdb.  First, is there already some simple way of interfacing with 
gdb to tell it to use our functions for managing processes and not its 
own?  If not, does patching gdb seem like a reasonable solution?  What 
would have to happen for these patches to get accepted into the official 
gdb?

   Regards, Johan Walles, Appeal Virtual Machines


             reply	other threads:[~2002-01-24 13:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-24  5:23 Johan Walles [this message]
2002-01-24  9:19 ` Daniel Jacobowitz
2002-01-24 23:23   ` Johan Walles
2002-01-24  9:21 ` Daniel Jacobowitz
2002-01-24  9:29   ` Andrew Cagney

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=3C500AAC.5030709@appeal.se \
    --to=johan.walles@appeal.se \
    --cc=gdb@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