|
Linux Forum Index » Linux Development - Applications » ltrace, strace but what tool for user calls ?...
Page 1 of 1
|
| Author |
Message |
| Robert... |
 Posted: Wed Aug 06, 2008 2:05 am |
|
|
|
Guest
|
Hi,
i'd like to trace a linux executable (which has debugng info). ltrace or
strace are goods, but the calls to the methods in the executable are not
showed. Is there a tool to get all this ? I don't want to use gdb, for
several reasons.
Thanks for any help. |
|
|
| Back to top |
|
| Andrei Voropaev... |
| Posted: Wed Aug 06, 2008 2:30 am |
|
|
|
Guest
|
On 2008-08-06, Josef Moellers <josef.moellers at (no spam) fujitsu-siemens.com> wrote:
Quote: Robert wrote:
i'd like to trace a linux executable (which has debugng info). ltrace or
strace are goods, but the calls to the methods in the executable are not
showed.
Where does ltrace fail?
ltrace shows only calls to dynamic libraries, not calls to functions within the
executable.
I guess the best tool here would be "printf"  I mean recompiling after
inserting printf in all interesting places. No other way really exists.
--
Minds, like parachutes, function best when open |
|
|
| Back to top |
|
| Josef Moellers... |
| Posted: Wed Aug 06, 2008 3:06 am |
|
|
|
Guest
|
Robert wrote:
Quote: Hi,
i'd like to trace a linux executable (which has debugng info). ltrace or
strace are goods, but the calls to the methods in the executable are not
showed. Is there a tool to get all this ? I don't want to use gdb, for
several reasons.
Where does ltrace fail?
--
These are my personal views and not those of Fujitsu Siemens Computers!
Josef Möllers (Pinguinpfleger bei FSC)
If failure had no penalty success would not be a prize (T. Pratchett)
Company Details: http://www.fujitsu-siemens.com/imprint.html |
|
|
| Back to top |
|
| Robert... |
| Posted: Wed Aug 06, 2008 4:19 am |
|
|
|
Guest
|
Josef Moellers a écrit :
Quote: Robert wrote:
Hi,
i'd like to trace a linux executable (which has debugng info). ltrace
or strace are goods, but the calls to the methods in the executable
are not showed. Is there a tool to get all this ? I don't want to use
gdb, for several reasons.
Where does ltrace fail?
Do you think ? I've found cygProfiler, but without the function
arguments, the trace is pretty useless... |
|
|
| Back to top |
|
| Josef Moellers... |
| Posted: Thu Aug 07, 2008 2:12 am |
|
|
|
Guest
|
Andrei Voropaev wrote:
Quote: On 2008-08-06, Josef Moellers <josef.moellers at (no spam) fujitsu-siemens.com> wrote:
Robert wrote:
i'd like to trace a linux executable (which has debugng info). ltrace or
strace are goods, but the calls to the methods in the executable are not
showed.
Where does ltrace fail?
ltrace shows only calls to dynamic libraries, not calls to functions within the
executable.
Oops ... yes, you're right. I never was really interested in the calls
to my own code, just the calls to the outside world ...
One learns new things every day.
Josef
--
These are my personal views and not those of Fujitsu Siemens Computers!
Josef Möllers (Pinguinpfleger bei FSC)
If failure had no penalty success would not be a prize (T. Pratchett)
Company Details: http://www.fujitsu-siemens.com/imprint.html |
|
|
| Back to top |
|
| Jasen Betts... |
| Posted: Fri Aug 15, 2008 4:39 am |
|
|
|
Guest
|
I missed the start of this thread
Quote: i'd like to trace a linux executable (which has debugng info). ltrace or
strace are goods, but the calls to the methods in the executable are not
showed.
valgrind
gdb
Bye.
Jasen |
|
|
| Back to top |
|
| |
