From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 11895 invoked by alias); 31 Jan 2002 20:43:03 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 11820 invoked from network); 31 Jan 2002 20:43:01 -0000 Received: from unknown (HELO cygnus.com) (205.180.230.5) by sources.redhat.com with SMTP; 31 Jan 2002 20:43:01 -0000 Received: from redhat.com (reddwarf.sfbay.redhat.com [205.180.231.12]) by runyon.cygnus.com (8.8.7-cygnus/8.8.7) with ESMTP id MAA19651; Thu, 31 Jan 2002 12:42:55 -0800 (PST) Message-ID: <3C59AABA.89270410@redhat.com> Date: Thu, 31 Jan 2002 12:43:00 -0000 From: Michael Snyder Organization: Red Hat, Inc. X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.4.2-2smp i686) X-Accept-Language: en MIME-Version: 1.0 To: "Sarnath K - CTD, Chennai." CC: gdb@sources.redhat.com Subject: Re: "xbreak" command in GDB ? References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-SW-Source: 2002-01/txt/msg00370.txt.bz2 "Sarnath K - CTD, Chennai." wrote: > > Hi All, > The "xbreak" command (and hence "txbreak" ) > in GDB Version 5.1 doesnt seem to work > properly. > A minute investigation showed that it is > setting a break-point at a posn > 1 past the last instrn of the "function". > Looks like a bug. Pardon me if I am wrong. > Maintainers can look into this. XBREAK is a mistake. It got in because the maintainers were not paying close enough attention (it was part of a really huge merge). It is completely non-portable, and there is probably no good way to make it portable. Nor does it do anything particularly useful (even if you can stop at the return instruction of a function, your stack frame will generally have been destroyed already). I'm going to propose a patch that will take xbreak out.