From: Peter Barada <peter@baradas.org>
To: smita@cse.ucsc.edu
Cc: brandner@emt.tugraz.at, gdb@sources.redhat.com
Subject: Re: return type of a fucntion
Date: Thu, 17 Apr 2003 03:37:00 -0000 [thread overview]
Message-ID: <20030417033746.2AEAA98982@baradas.org> (raw)
In-Reply-To: <Pine.GSO.4.44.0304161249140.12775-100000@sundance.cse.ucsc.edu> (message from Smita on Wed, 16 Apr 2003 12:49:59 -0700 (PDT))
>Hi,
>When I print $r3 on returning from a function, I get the return value. But
>is there a way to get the type of the return value (eg. whether it is a
>pointer or an interger)??
If you know which function you're in, you could always 'ptype
functionName' where 'fuctionName' is replaced with the function's name
and you'll see the type that the function returns. Then you could cast
$r3 to that type. Of course this doesn't works so well with
float/double as well as structures.
--
Peter Barada
peter@baradas.org
next prev parent reply other threads:[~2003-04-17 3:37 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-16 18:18 gdb refuses to 'break' Markus Brandner
2003-04-16 19:51 ` return type of a fucntion Smita
2003-04-16 19:59 ` gdb's communication to a process/libgdb? Smita
2003-04-16 20:04 ` Daniel Jacobowitz
2003-04-16 22:07 ` libgdb Smita
2003-04-16 23:58 ` is libgdb okay to use? Smita
2003-04-17 1:44 ` libgdb Elena Zannoni
2003-04-17 2:06 ` libgdb Smita
2003-04-17 2:12 ` finish implementation Smita
2003-04-17 12:57 ` libgdb Elena Zannoni
2003-04-17 2:11 ` finish for nested function calls Smita
2003-04-17 3:37 ` Peter Barada [this message]
2003-04-17 9:13 ` gdb refuses to 'break' Markus Brandner
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=20030417033746.2AEAA98982@baradas.org \
--to=peter@baradas.org \
--cc=brandner@emt.tugraz.at \
--cc=gdb@sources.redhat.com \
--cc=smita@cse.ucsc.edu \
/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).