This is the mail archive of the java-patches@gcc.gnu.org mailing list for the Java project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: [JVMTI] RFA: JVMTI Stack Tracing

From: Kyle Galloway <kgallowa at redhat dot com>
To: java-patches at gcc dot gnu dot org
Date: Fri, 20 Oct 2006 11:30:12 -0400
Subject: Re: [JVMTI] RFA: JVMTI Stack Tracing
References: <4538D434.90208@redhat.com> <4538E40A.7060602@avtrex.com>

David Daney wrote:

Is libc async-signal safe? What happens if the unwinder cannot produce a stacktrace because the thread was stopped somewhere where there was no unwind info?

Why don't you set SA_RESTART?

Why SIGTRAP? That will interact poorly with gdb.

David Daney

I should have set, SA_RESTART, I'll change that. As for SIGTRAP, there was no real reason, I could use any of a bunch of different signals, maybe SIGPWR would be a better choice?

- Kyle

Follow-Ups:
- Re: [JVMTI] RFA: JVMTI Stack Tracing
  - From: Hans Boehm

References:
- [JVMTI] RFA: JVMTI Stack Tracing
  - From: Kyle Galloway
- Re: [JVMTI] RFA: JVMTI Stack Tracing
  - From: David Daney

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]