From: Daniel Jacobowitz <drow@false.org>
To: Neo <cjia@cse.unl.edu>
Cc: gdb <gdb@sourceware.org>
Subject: Re: Lots of SIGFPE and SIGSEGV found while debugging Sun hotspot vm on AMD64 machine
Date: Thu, 22 Mar 2007 17:46:00 -0000 [thread overview]
Message-ID: <20070322174636.GA11602@caradoc.them.org> (raw)
In-Reply-To: <4602C5DA.8040000@cse.unl.edu>
On Thu, Mar 22, 2007 at 12:07:22PM -0600, Neo wrote:
> hi,
> Everything is fine when I am using gdb to debug Sun hotspot VM on IA32 machine.
> But something wired happens on AMD64 machine. Since the code executed on VM is
> dynamically generated I cannot get any information from the "bt" command. Is
> there any other approach to debug? Without attaching gdb, there is no error. I
> am using the latest version gdb from CVS.
It's probably generating those signals deliberately. Try using
"handle" to pass and ignore them. That's fairly common for JVMs.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2007-03-22 17:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-22 17:07 Neo
2007-03-22 17:46 ` Daniel Jacobowitz [this message]
[not found] ` <1174589384.9964.17.camel@localhost.localdomain>
2007-03-22 20:34 ` Lots of SIGFPE and SIGSEGV found while debugging Sun hotspotvm " Neo
2007-03-22 21:19 ` Michael Snyder
2007-03-23 2:15 ` Neo
2007-03-22 17:26 Lots of SIGFPE and SIGSEGV found while debugging Sun hotspot vm " Jude Moersdorf
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=20070322174636.GA11602@caradoc.them.org \
--to=drow@false.org \
--cc=cjia@cse.unl.edu \
--cc=gdb@sourceware.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