From: Jonathan Larmour <jlarmour@redhat.com>
To: "Trenton D. Adams" <tadams@extremeeng.com>
Cc: 'eCos discussion' <ecos-discuss@sources.redhat.com>
Subject: Re: [ECOS] Forcing a Break in code
Date: Wed, 27 Jun 2001 10:00:00 -0000 [thread overview]
Message-ID: <3B3A110D.F4E1D54E@redhat.com> (raw)
In-Reply-To: <000a01c0ff23$d258d830$090110ac@TRENT>
"Trenton D. Adams" wrote:
>
> I want to get my program to break before a certain location by calling
> some sort of function? Is that possible?
You mean forcibly hit a GDB breakpoint? You can use the breakpoint()
function if you have GDB stubs included in your app. Note you will have to
manually step over it if you want to continue.
Jifl
--
Red Hat, Rustat House, Clifton Road, Cambridge, UK. Tel: +44 (1223) 271062
Maybe this world is another planet's Hell -Aldous Huxley || Opinions==mine
Come to the Red Hat TechWorld open source conference in Brussels!
Keynotes, techie talks and exhibitions http://www.redhat-techworld.com/
prev parent reply other threads:[~2001-06-27 10:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-27 9:12 Trenton D. Adams
2001-06-27 10:00 ` Jonathan Larmour [this message]
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=3B3A110D.F4E1D54E@redhat.com \
--to=jlarmour@redhat.com \
--cc=ecos-discuss@sources.redhat.com \
--cc=tadams@extremeeng.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).