This is the mail archive of the
mailing list for the GDB project.
Re: "xbreak" command in GDB ?
- From: Michael Snyder <msnyder at redhat dot com>
- To: "Sarnath K - CTD, Chennai." <k_sarnath at ctd dot hcltech dot com>
- Cc: gdb at sources dot redhat dot com
- Date: Thu, 31 Jan 2002 12:36:10 -0800
- Subject: Re: "xbreak" command in GDB ?
- Organization: Red Hat, Inc.
- References: <EF836A380096D511AD9000B0D021B52754AE83@narmada.ctd.hcltech.com>
"Sarnath K - CTD, Chennai." wrote:
> Hi All,
> The "xbreak" command (and hence "txbreak" )
> in GDB Version 5.1 doesnt seem to work
> 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.