Replying to all. Or you can set a timer which interrupts and checks the stack and prints stack out. But you will get address of the instruction in the function.
you can see dtrace concept of hacking stack to insert callback functions to trace callee. Regards, Sri. On Sat, Sep 18, 2010 at 10:42 PM, Mulyadi Santosa <mulyadi.sant...@gmail.com > wrote: > Hi.. > > On Sun, Sep 19, 2010 at 08:50, Vimal <j.vi...@gmail.com> wrote: > > Most of the times, I just end up tracing the code path manually from > > the source code. I have another question, though: Is it possible in > > gdb to break on all function calls? Would be useful. :) > > > None that I know :) But maybe that is doable inside system emulator > such as Qemu. You need to trap the call of "call", "far jmp" or things > like that. But the problem here is it is done system widely...thus you > need a way to selectively filter which function calls you want to trap > and which ones are not > > -- > regards, > > Mulyadi Santosa > Freelance Linux trainer and consultant > > blog: the-hydra.blogspot.com > training: mulyaditraining.blogspot.com > > -- > To unsubscribe from this list: send an email with > "unsubscribe kernelnewbies" to ecar...@nl.linux.org > Please read the FAQ at http://kernelnewbies.org/FAQ > > -- Regards, Sri.
