From: Michael Snyder <msnyder@redhat.com>
To: Eli Zaretskii <eliz@is.elta.co.il>
Cc: k_sarnath@ctd.hcltech.com, gdb@sources.redhat.com
Subject: Re: "xbreak" command in GDB ?
Date: Thu, 31 Jan 2002 12:39:00 -0000 [thread overview]
Message-ID: <3C59A9CC.5B4392E1@redhat.com> (raw)
In-Reply-To: <6137-Fri25Jan2002094510+0200-eliz@is.elta.co.il>
Eli Zaretskii wrote:
>
> > From: "Sarnath K - CTD, Chennai." <k_sarnath@ctd.hcltech.com>
> > Date: Thu, 24 Jan 2002 14:59:18 +0530
> >
> > The "xbreak" command (and hence "txbreak" )
> > in GDB Version 5.1 doesnt seem to work
> > properly.
>
> What OS? What compiler?
XBREAK was added by HP, in a completely non-portable way,
and the maintainers did not catch it. When I can find a
spare moment, I am going to post a patch recommending
its removal.
> On my system (DJGPP, GCC 3.0.2), xbreak does seem to work.
If you look at how XBREAK is implemented, you will see
that if it works at all it is sheer coincidence, and it
doesn't really do anything useful even then. The best it
may do is stop you at the return instruction, and by then
your stack frame will have been destroyed.
> > A minute investigation showed that it is
> > setting a break-point at a posn
> > 1 past the last instrn of the "function".
>
> Could you send a complete short test program and a sequence of
> commands, including the compilation command line, to reproduce that?
next prev parent reply other threads:[~2002-01-31 20:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-24 1:33 Sarnath K - CTD, Chennai.
2002-01-24 23:46 ` Eli Zaretskii
2002-01-25 0:27 ` Pierre Muller
2002-01-31 12:45 ` Michael Snyder
2002-01-31 12:39 ` Michael Snyder [this message]
2002-01-31 12:43 ` Michael Snyder
2002-01-25 0:24 Sarnath K - CTD, Chennai.
2002-01-25 0:33 Sarnath K - CTD, Chennai.
[not found] <EF836A380096D511AD9000B0D021B52754B482@narmada.ctd.hcltech .com>
2002-01-25 1:20 ` Pierre Muller
2002-01-28 11:18 ` Elena Zannoni
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3C59A9CC.5B4392E1@redhat.com \
--to=msnyder@redhat.com \
--cc=eliz@is.elta.co.il \
--cc=gdb@sources.redhat.com \
--cc=k_sarnath@ctd.hcltech.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox