From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6103 invoked by alias); 28 Aug 2014 10:58:56 -0000 Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org Received: (qmail 6093 invoked by uid 89); 28 Aug 2014 10:58:55 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.2 required=5.0 tests=AWL,BAYES_00,RP_MATCHES_RCVD,SPF_PASS autolearn=ham version=3.3.2 X-HELO: mailhost.allinea.com Received: from mailhost.allinea.com (HELO mailhost.allinea.com) (94.125.131.203) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Thu, 28 Aug 2014 10:58:53 +0000 Received: from [192.168.0.130] (cpc10-sotn11-2-0-cust104.15-1.cable.virginm.net [82.19.61.105]) (Authenticated sender: cjanuary) by mailhost.allinea.com (Postfix) with ESMTPSA id 2E74B2006DF; Thu, 28 Aug 2014 11:56:46 +0100 (BST) Message-ID: <1409223530.3407.15.camel@chris-xps13> Subject: Re: catch signal does not appear multi-inferior safe From: Chris January To: Pedro Alves Cc: gdb@sourceware.org Date: Thu, 28 Aug 2014 10:58:00 -0000 In-Reply-To: <53F36F39.8090201@redhat.com> References: <1405076204.3524.8.camel@chris-xps13> <53F36F39.8090201@redhat.com> Content-Type: text/plain; charset="UTF-8" Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-IsSubscribed: yes X-SW-Source: 2014-08/txt/msg00133.txt.bz2 Hello Pedro, On Tue, 2014-08-19 at 16:37 +0100, Pedro Alves wrote: > On 07/11/2014 11:56 AM, Chris January wrote: > > It appears to me that the 'catch signal' support in GDB is not > > multi-inferior safe. Combining the 'catch signal' command with the > > 'checkpoint' command, for example, results in an internal error: > > > > break-catch-sig.c:152: internal-error: > > signal_catchpoint_remove_location: Assertion `signal_catch_counts[iter] > >> 0' failed. > > A problem internal to GDB has been detected, > > further debugging may prove unreliable. > > Quit this debugging session? (y or n) > > > > see the end of this e-mail for reproducer. > > > > When checkpointing / catching a fork signal_catchpoint_remove_location > > may be called twice in a row - once for the parent and once for the > > child. > > Signal catchpoint locations aren't really per-process; they're > global. GDB shouldn't be trying to detach them from the child. > Where is this happening? Is this from detach_breakpoint ? That's > odd, since that skips bp_loc_other locations? You are right. I was testing with an old version of GDB (7.6.2). It is fixed in recent versions by this commit: commit bd9673a4ded96ea5c108601501c8e59003ea1be6 Author: Philippe Waroquiers Date: Tue May 21 18:47:05 2013 +0000 Fix internal error caused by interaction between catch signal and fork Sorry for the noise! Regards, Chris