From: Peter Barada <peter@the-baradas.com>
To: Malcolm_Barrows@eur.3com.com
Cc: gdb@sources.redhat.com
Subject: Re: Run arguments
Date: Thu, 22 Apr 2004 16:30:00 -0000 [thread overview]
Message-ID: <20040422151952.9F0E998C8A@baradas.org> (raw)
In-Reply-To: <80256E7E.004FD1CA.00@notesmta.eur.3com.com> (Malcolm_Barrows@eur.3com.com)
>Forgive the ignorance level for the following question
>
>I am using gdb for debugging an embedded C application.
>I can call numerous embedded functions and pass parameters to it, add
>breakpoints and step
>through the code - so far so good.
>
>Some of the functions return values as part of their functionality
>
>as in
>
>int MYFUNCTION ( suppliedparam, rtndparam)
>{
> some code ......
>
> return (rtndparam)
>
>}
>
>The question is
>How do I get to get the value of returned parameters output to the command line.
>
>i.e in the above example I want to know what the value of rtndparam is
Place a breakpoint on the return statement, run the program and at the
breakpoint, type "print rtndparam".
--
Peter Barada
peter@the-baradas.com
prev parent reply other threads:[~2004-04-22 15:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-22 14:47 Malcolm Barrows
2004-04-22 16:30 ` Peter Barada [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=20040422151952.9F0E998C8A@baradas.org \
--to=peter@the-baradas.com \
--cc=Malcolm_Barrows@eur.3com.com \
--cc=gdb@sources.redhat.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