From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15476 invoked by alias); 29 Apr 2006 14:20:48 -0000 Received: (qmail 15458 invoked by uid 22791); 29 Apr 2006 14:20:47 -0000 X-Spam-Check-By: sourceware.org Received: from romy.inter.net.il (HELO romy.inter.net.il) (192.114.186.66) by sourceware.org (qpsmtpd/0.31) with ESMTP; Sat, 29 Apr 2006 14:20:44 +0000 Received: from HOME-C4E4A596F7 (IGLD-80-230-198-67.inter.net.il [80.230.198.67]) by romy.inter.net.il (MOS 3.7.3-GA) with ESMTP id EBQ27341 (AUTH halo1); Sat, 29 Apr 2006 17:20:41 +0300 (IDT) Date: Sat, 29 Apr 2006 14:20:00 -0000 Message-Id: From: Eli Zaretskii To: Joel Brobecker CC: gdb-patches@sources.redhat.com In-reply-to: <20060428171154.GP17613@adacore.com> (message from Joel Brobecker on Fri, 28 Apr 2006 10:11:54 -0700) Subject: Re: [RFC/RFA/i386] pb reading insns if breakpoints still inserted Reply-to: Eli Zaretskii References: <20060428171154.GP17613@adacore.com> X-IsSubscribed: yes Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2006-04/txt/msg00386.txt.bz2 > Date: Fri, 28 Apr 2006 10:11:54 -0700 > From: Joel Brobecker > > The fix that has been suggested is to fix the i386 prologue analyzer > to handle inserted breakpoints. This is what the new read_insn() > function does. Isn't this a general problem, not limited to x86? That is, if there's a breakpoint inserted in the prologue, wouldn't other prologue analyzers be fooled? If this is indeed a general problem, I suggest we fix it in a general fashion, not for some specific platform.