Retrieving function parameters

[anirbid.banerjee]

Hi List,

This question can be categorised under "C programming in Linux", but
as I didnt find any group of that sort, I post it here.

I have a small program to print the stack trace of a particular
function. Here is the code:
=============== =============== =============== =======
#include <stdio.h>
#include <execinfo.h>
#include <stdlib.h>

void print_trace (void){
void *arr[20];
size_t asize, icnt;
char **str;

asize = backtrace (arr, 20);
str = backtrace_symbo ls (arr, asize);
for (icnt=0; icnt<asize; ++icnt)
printf ("%s\n",str[icnt]);
free (str);
}
int main(int argc, char **argv)
{
print_trace ();
return 0;
}
=============== =============== =============== =======
By calling backtrace ( ) and backtrace_symbo ls ( ) I can get a trace
of the calling functions path.
What I would like to know is if I can find the contents of the calling
functions () s argument values too?

More precisely:

A(void) {
....
backtrace ( )
backtrace_symbo ls ( )
....
}

B (int foo, int bar){
A () ;
....
}

C (int foo, int bar, int baz){
B ();
....
}

int main (){
C ()
....
....
}

>From the backtrace_symbo ls we can generate a path of the function call

main() calling C ()-C() calling B() -B() calling A(). Can we also
get the values for the arguments used in C (foo, bar, baz) and B (foo,
bar)? If we could then how?

Thanks
Anirbid

[mark_bluemel]

On 9 Feb, 13:11, "anirbid.baner. [e-mail]"
<anirbid.baner. [e-mail] te:

Hi List,

This question can be categorised under "C programming in Linux", but
as I didnt find any group of that sort, I post it here.

<Off-topic>
It's actually a question about the GNU libc library, and is strictly
speaking off-topic here.

One of the GNU mailing lists might be an appropriate place to ask.

http://www.gnu.org/software/libc/man...acktraces.html
seems to cover what it can do.

Accessing function arguments isn't on the list. It would be difficult
to provide in any optimised situation, I'd have thought.
</Off-topic>

[jacob navia]

an************* *@gmail.com wrote:

Hi List,

This question can be categorised under "C programming in Linux", but
as I didnt find any group of that sort, I post it here.

I have a small program to print the stack trace of a particular
function. Here is the code:
=============== =============== =============== =======
#include <stdio.h>
#include <execinfo.h>
#include <stdlib.h>

void print_trace (void){
void *arr[20];
size_t asize, icnt;
char **str;

asize = backtrace (arr, 20);
str = backtrace_symbo ls (arr, asize);
for (icnt=0; icnt<asize; ++icnt)
printf ("%s\n",str[icnt]);
free (str);
}
int main(int argc, char **argv)
{
print_trace ();
return 0;
}
=============== =============== =============== =======
By calling backtrace ( ) and backtrace_symbo ls ( ) I can get a trace
of the calling functions path.
What I would like to know is if I can find the contents of the calling
functions () s argument values too?

More precisely:

A(void) {
...
backtrace ( )
backtrace_symbo ls ( )
...
}

B (int foo, int bar){
A () ;
...
}

C (int foo, int bar, int baz){
B ();
...
}

int main (){
C ()
...
...
}

>>From the backtrace_symbo ls we can generate a path of the function call

main() calling C ()-C() calling B() -B() calling A(). Can we also
get the values for the arguments used in C (foo, bar, baz) and B (foo,
bar)? If we could then how?

Thanks
Anirbid

Of course you can. You have just to write a debugger.

To know what the values in the stack *are* you have to know the
type of the arguments. THEN and only then, you can interpret
the bits in the stack in a meaningful fashion. If not, you can just
see some bits but you have no idea of what they represent.

Besides, you have to know that the values start at a certain offset from
the stack, the organization of stack/frame pointer, and several other
interesting things.

Writing a debugger is a lot of fun. Lcc-win32's debugger costed me some
pain, but it was worth.

It is not a completely general debugger of course. I have
never tested it outside lcc-win32, and I suppose that you have enough
time to write a differeent debugger for each compiler you will use.

Debug information formats vary a lot. Microsoft used NB09 in Windows 98
and changed to NB10 in windows 2000. I use NB09 since I did not see why
I should change.

Gcc uses a different format called "stabs", under windows, and in the
old versions of linux. Now the changed to DWARF, leaving the stabs format.

Under linux, I use the stabs format, and DWARF when there is no other
choice.

But there is also not only the debug information format that changes.
You have to know that the frame pointer organization
changes considerably if you are in optimized code or not.

This could throw off many of your offsets if you do not take care.

But it is a fun project.

[Flash Gordon]

ma**********@po box.com wrote, On 09/02/07 13:29:

On 9 Feb, 13:11, "anirbid.baner. [e-mail]"
<anirbid.baner. [e-mail] te:

>Hi List,

This question can be categorised under "C programming in Linux", but
as I didnt find any group of that sort, I post it here.

<Off-topic>
It's actually a question about the GNU libc library, and is strictlybe a good place to look.
speaking off-topic here.

<snip>

The linux application development groups would probably be a good place
to ask after checking the relevant FAQ of course.
--
Flash Gordon

[CBFalconer]

"an************ **@gmail.com" wrote:

>
This question can be categorised under "C programming in Linux",
but as I didnt find any group of that sort, I post it here.

I have a small program to print the stack trace of a particular
function. Here is the code:
=============== =============== =============== =======
#include <stdio.h>
#include <execinfo.h>
#include <stdlib.h>

.... snip ...

>
From the backtrace_symbo ls we can generate a path of the function
call main() calling C ()-C() calling B() -B() calling A().
Can we also get the values for the arguments used in C (foo, bar,
baz) and B (foo, bar)? If we could then how?

First, this is not a C question. Try comp.unix.progr ammer. There
is no such thing as <execinfo.het c. in standard C.

Second, C parameters are passed by value, and may be freely
modified. Thus, even if you can see the present value of those
parameters, there is no guarantee that those are the passed-in
values.

--
<http://www.cs.auckland .ac.nz/~pgut001/pubs/vista_cost.txt>
<http://www.securityfoc us.com/columnists/423>

"A man who is right every time is not likely to do very much."
-- Francis Crick, co-discover of DNA
"There is nothing more amazing than stupidity in action."
-- Thomas Matthews

[Stephen Sprunk]

<an************ **@gmail.comwro te in message
news:11******** *************@j 27g2000cwj.goog legroups.com...

Hi List,

This question can be categorised under "C programming in Linux", but
as I didnt find any group of that sort, I post it here.

comp.unix.progr ammer would be a good start for anything POSIX. There's
also several Linux newsgroups under comp.os.linux.

From the backtrace_symbo ls we can generate a path of the function call
main() calling C ()-C() calling B() -B() calling A(). Can we also
get the values for the arguments used in C (foo, bar, baz) and B (foo,
bar)? If we could then how?

You probably can't do it, and if you can it certainly won't be portable.
There's no guarantee that the calling functions' arguments still exist,
as they may have been passed in registers (depending on the platform) or
their location on the stack may have been reused for other purposes.
You're lucky to get the function call path, and that isn't portable
either.

If you need those details, your best bet is a debugger.

S

--
Stephen Sprunk "God does not play dice." --Albert Einstein
CCIE #3723 "God is an inveterate gambler, and He throws the
K5SSS dice at every possible opportunity." --Stephen Hawking
--
Posted via a free Usenet account from http://www.teranews.com