Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Mohsen Pahlevanzadeh <mohsen@pahlevanzadeh.org>
To: Markus Duft <mduft@gentoo.org>
Cc: gdb@sourceware.org
Subject: Re: binary debugging and generate source of which that running
Date: Thu, 07 Jul 2011 15:24:00 -0000	[thread overview]
Message-ID: <1310052214.2313.2.camel@debian> (raw)
In-Reply-To: <4E15B8DA.1090906@gentoo.org>

[-- Attachment #1: Type: text/plain, Size: 1104 bytes --]

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 #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 316 bytes --]

  reply	other threads:[~2011-07-07 15:24 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-06 20:52 see automatically source Mohsen Pahlevanzadeh
2011-07-07  4:38 ` binary debugging and generate source of which that running Mohsen Pahlevanzadeh
2011-07-07  7:20   ` harish badrinath
2011-07-07  8:46     ` Mohsen Pahlevanzadeh
2011-07-07  8:48       ` harish badrinath
2011-07-07  9:15         ` Mohsen Pahlevanzadeh
2011-07-07  9:23           ` Jan Kratochvil
2011-07-07  9:29             ` Mohsen Pahlevanzadeh
2011-07-07 12:33           ` Andrew Burgess
2011-07-07 13:47             ` Markus Duft
2011-07-07 15:24               ` Mohsen Pahlevanzadeh [this message]
2011-07-07 15:26             ` Mohsen Pahlevanzadeh
2011-07-08  5:15 ` see automatically source Paul Pluzhnikov

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=1310052214.2313.2.camel@debian \
    --to=mohsen@pahlevanzadeh.org \
    --cc=gdb@sourceware.org \
    --cc=mduft@gentoo.org \
    /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