This is the mail archive of the gdb-patches@sources.redhat.com mailing list for the GDB 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: [commit] Check undebuggable after sigtramp; Was: [patch/rfc] Useinsert_step_resume_breakpoint everywhere

From: Mark Kettenis <kettenis at chello dot nl>
To: cagney at gnu dot org
Cc: gdb-patches at sources dot redhat dot com
Date: Thu, 13 May 2004 21:52:43 +0200 (CEST)
Subject: Re: [commit] Check undebuggable after sigtramp; Was: [patch/rfc] Useinsert_step_resume_breakpoint everywhere
References: <40A01953.7060906@gnu.org> <40A161F4.6050801@gnu.org> <200405122029.i4CKT0r4006056@elgar.kettenis.dyndns.org> <40A28D7B.90007@gnu.org> <40A3CF09.70807@gnu.org>

   Date: Thu, 13 May 2004 15:39:53 -0400
   From: Andrew Cagney <cagney@gnu.org>

   Per the attached I've done this, I'm no longer seeing the panic.

Works for me too.  By the way, it was FreeBSD 4.7-RELEASE-p20 that was
showing the problem.

Mark

References:
- [patch/rfc] Use insert_step_resume_breakpoint everywhere
  - From: Andrew Cagney
- Re: [patch/rfc] Use insert_step_resume_breakpoint everywhere
  - From: Andrew Cagney
- Re: [patch/rfc] Use insert_step_resume_breakpoint everywhere
  - From: Mark Kettenis
- Re: [patch/rfc] Use insert_step_resume_breakpoint everywhere
  - From: Andrew Cagney
- [commit] Check undebuggable after sigtramp; Was: [patch/rfc] Useinsert_step_resume_breakpoint everywhere
  - From: Andrew Cagney

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