Re: breakpoints/1738: Single stepping and signals don't interactwell

[Andrew Cagney <ac131313 at redhat dot com>]

The following reply was made to PR breakpoints/1738; it has been noted by GNATS.

From: Andrew Cagney <ac131313@redhat.com>
To: gdb-gnats@sources.redhat.com
Cc:  
Subject: Re: breakpoints/1738: Single stepping and signals don't interact
 well
Date: Wed, 25 Aug 2004 14:02:01 -0400

 Can you add the output from
 
 	(gdb) set debug target 1
 
 for the step case?
 
 I'm reading this:
 
 > This leads to creating a breakpoint and calling keep_going.  But breakpoints are not inserted so the new breakpoint is not inserted.  keep_going causes us to single-step again,
 > but deliver the SIGALRM.  Breakpoints are removed, so we stop after handler has run [oops].  At this point trap_expected is set (it was set in proceed because we were stepping over a breakpoint).  Normally we would see that we have stepped out of the stepping range and stop... but step_resume_breakpoint is set.  This triggers:
 
 to mean that you see:
 
 	target_resume (-1, step, SIGALRM)
 
 in the output.
 
 Andrew