From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16868 invoked by alias); 18 Aug 2008 12:42:48 -0000 Received: (qmail 16860 invoked by uid 22791); 18 Aug 2008 12:42:47 -0000 X-Spam-Check-By: sourceware.org Received: from NaN.false.org (HELO nan.false.org) (208.75.86.248) by sourceware.org (qpsmtpd/0.31) with ESMTP; Mon, 18 Aug 2008 12:42:08 +0000 Received: from nan.false.org (localhost [127.0.0.1]) by nan.false.org (Postfix) with ESMTP id 3B754983A9; Mon, 18 Aug 2008 12:42:07 +0000 (GMT) Received: from caradoc.them.org (22.svnf5.xdsl.nauticom.net [209.195.183.55]) by nan.false.org (Postfix) with ESMTP id A504498337; Mon, 18 Aug 2008 12:42:06 +0000 (GMT) Received: from drow by caradoc.them.org with local (Exim 4.69) (envelope-from ) id 1KV43h-0001tW-Kf; Mon, 18 Aug 2008 08:42:05 -0400 Date: Mon, 18 Aug 2008 18:30:00 -0000 From: Daniel Jacobowitz To: Antony KING Cc: Ulrich Weigand , gdb@sourceware.org Subject: Re: Spurious SIGTRAP reported by GDB 6.8 when debugging embedded RTOS application Message-ID: <20080818124205.GA6958@caradoc.them.org> Mail-Followup-To: Antony KING , Ulrich Weigand , gdb@sourceware.org References: <200808152315.m7FNFeMU025871@d12av02.megacenter.de.ibm.com> <48A94CE7.8010400@st.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <48A94CE7.8010400@st.com> User-Agent: Mutt/1.5.17 (2008-05-11) X-IsSubscribed: yes 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 X-SW-Source: 2008-08/txt/msg00217.txt.bz2 On Mon, Aug 18, 2008 at 11:20:23AM +0100, Antony KING wrote: > Thanks for the explanation. Unfortunately GDB has no influence over the > RTOS, it is merely an observer. This means that it cannot change the > status of threads or decide which thread is to execute; this is solely > under the control of the RTOS. If GDB has requested a step for a particular thread, and you're enabling hardware single step in your stub while another thread is current, I think this must be a bug in the stub. It should, at the least, report an error instead of continuing. That said, GDB hasn't been used in this way in a while, though it used to support it. I think you'll need to communicate to GDB somehow that it can not change the executing thread. -- Daniel Jacobowitz CodeSourcery