This is the mail archive of the gdb@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: binary debugging and generate source of which that running


Yes, Of course,For instance, if your program run function myfunc()
agains signal OOO, i can see source of myfunc and name of myfunc(), of
course, name of function is very important.
--mohsen

On Thu, 2011-07-07 at 15:47 +0200, Markus Duft wrote:
> On 07/07/11 14:32, Andrew Burgess wrote:
> > On 07/07/2011 10:14, Mohsen Pahlevanzadeh wrote:
> >> You suppose my program has 10 functions, and my program in running now
> >> by gdb, i wanna know when i send signal x y z to my program, myprgram
> >> call which function, So i need to a command same as list but immediately
> >> print source of peace of running.
> > 
> > Maybe "handle" is what you want?
> >   http://sourceware.org/gdb/current/onlinedocs/gdb/Signals.html#Signals
> > 
> > You can arrange to stop on each signal x, y, and z, then step into the handlers for each as they arrive.
> 
> As i understood it, he wants to be able to see whats happening as the program executes normally, much like a strace or truss, but printing the according source information. is this correct?
> 
> Markus
> 
> > 
> > Andrew
> > 
> 

Attachment: signature.asc
Description: This is a digitally signed message part


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]