From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 13410 invoked by alias); 30 Oct 2004 14:54:27 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 13403 invoked from network); 30 Oct 2004 14:54:26 -0000 Received: from unknown (HELO localhost.redhat.com) (24.42.65.225) by sourceware.org with SMTP; 30 Oct 2004 14:54:26 -0000 Received: from [127.0.0.1] (localhost.localdomain [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id A1B5F129D8C; Sat, 30 Oct 2004 09:54:21 -0400 (EDT) Message-ID: <41839D0D.8070700@gnu.org> Date: Sat, 30 Oct 2004 19:48:00 -0000 From: Andrew Cagney User-Agent: Mozilla Thunderbird 0.8 (X11/20041020) MIME-Version: 1.0 To: Andreas Schwab Cc: Andrew Cagney , gdb@sources.redhat.com Subject: Re: infrun.c:2642: internal-error: insert_step_resume_breakpoint_at_sal: Assertion `step_resume_breakpoint == NULL' failed. References: <418280F3.1090502@redhat.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2004-10/txt/msg00428.txt.bz2 Andreas Schwab wrote: > Andrew Cagney writes: > > >>Andreas Schwab wrote: >> >>>I'm getting this assertion failure on ia64-linux when stepping after a >>>breakpoint with a signal also being delivered. Both calls to >>>insert_step_resume_breakpoint_at_sal are coming from the two calls to >>>insert_step_resume_breakpoint_at_frame in handle_inferior_event. In both >>>calls the actual address where the breakpoint is to be set is the same. I >>>haven't been able to come up with a small test case, this happens while >>>debugging Emacs. >> >>The sig* tests check this edge case. > > > Not this one. There are only two failures, which are > "gdb.base/sigstep.exp: finish from handleri; leave handler (timeout)" and > "gdb.base/sigstep.exp: finish from handleri; leave signal trampoline", and > neither are not due to internal errors. The "step on breakpoint; ..." tests, based on your description, exercise just that senario. They run to a breakpoint, wait for a signal to be come pending, and then try to step et.al. Sounds like more is going on? Andrew Ref 1757, 1738