From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 899 invoked by alias); 7 May 2010 18:53:11 -0000 Received: (qmail 885 invoked by uid 48); 7 May 2010 18:53:11 -0000 Date: Fri, 07 May 2010 18:53:00 -0000 Message-ID: <20100507185311.884.qmail@sourceware.org> From: "k04jg02 at gmail dot com" To: gdb-prs@sourceware.org In-Reply-To: <20100507184945.11581.k04jg02@gmail.com> References: <20100507184945.11581.k04jg02@gmail.com> Reply-To: sourceware-bugzilla@sourceware.org Subject: [Bug threads/11581] 'set scheduler-locking on' should be automatic in response to SIGABRT and SIGSEGV X-Bugzilla-Reason: CC Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-prs-owner@sourceware.org X-SW-Source: 2010-q2/txt/msg00229.txt.bz2 ------- Additional Comments From k04jg02 at gmail dot com 2010-05-07 18:53 ------- Also, due to some platforms supporting scheduler-locking and some not, and due to developers that may use GDB across multiple platforms, it might be a good idea to print a message when it's *not* being enabled in response to SIGABRT/SIGSEGV due to lack of support, so that developers are aware GDB may act differently than they're accustomed to from working on another platform. -- http://sourceware.org/bugzilla/show_bug.cgi?id=11581 ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.