From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6390 invoked by alias); 25 Jan 2008 14:11:20 -0000 Received: (qmail 6381 invoked by uid 22791); 25 Jan 2008 14:11:20 -0000 X-Spam-Check-By: sourceware.org Received: from kuber.nabble.com (HELO kuber.nabble.com) (216.139.236.158) by sourceware.org (qpsmtpd/0.31) with ESMTP; Fri, 25 Jan 2008 14:10:04 +0000 Received: from isper.nabble.com ([192.168.236.156]) by kuber.nabble.com with esmtp (Exim 4.63) (envelope-from ) id 1JIPFq-0001SO-LB for gdb@sourceware.org; Fri, 25 Jan 2008 06:10:02 -0800 Message-ID: <15088448.post@talk.nabble.com> Date: Fri, 25 Jan 2008 14:11:00 -0000 From: Guillaume MENANT To: gdb@sourceware.org Subject: Stop reply packet behaviour MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-From: guillaume.menant@geensys.com 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-01/txt/msg00256.txt.bz2 Hello, I'm wondering what should be the stop reply packet content when my software breaks on a software breakpoint. Does the stop reply reason has to be "watch" followed by the current PC or something else ? Thanks. -- View this message in context: http://www.nabble.com/Stop-reply-packet-behaviour-tp15088448p15088448.html Sent from the Sourceware - gdb list mailing list archive at Nabble.com.