Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Sergio Durigan Junior <sergiodj@redhat.com>
To: "Vardhana\, Ananda" <ananda.vardhana@intel.com>
Cc: "gdb\@sourceware.org" <gdb@sourceware.org>
Subject: Re: Questions on vCont
Date: Mon, 09 Jun 2014 23:26:00 -0000	[thread overview]
Message-ID: <m34mzt7jhm.fsf@redhat.com> (raw)
In-Reply-To: <301B88517A226B4DA3D210EF3D49753273F76D16@ORSMSX102.amr.corp.intel.com>	(Ananda Vardhana's message of "Mon, 9 Jun 2014 17:39:37 +0000")

Hi Ananda,

On Monday, June 09 2014, Ananda Vardhana wrote:

> Could some kind folk clear up some of my doubts:
>
> 1.      "Resume the inferior, specifying different actions for each thread" --> what does this first sentence mean? What does word inferior mean in this context?

Inferior is the GDB parlance for the program being debugged.

> 2.      "Specifying multiple default actions is an error" -->   Please give me couple of examples.

I have answered this one in private.

> 3.      "specifying no actions is also an error". An example for this too please.

Likewise.

> 4.      Lastly please tell me what all commands I have specified here is wrong
> a.      vCont;c:ab;c:cd --> ab, cd are thread id's
> b.      vCont;c:12;s:23;t:45
> c.      vCont;c:3;s:3 --> This is wrong for sure
> d.      vCont;c-1 --> Putting anything after this wrong as we have continue on all processors

On (d) you're missing a colon between "c" and "-1" (I think I already
answered this one before, too).

>
> 'C sig'
>
>       Continue with signal sig. The signal sig should be two hex digits.
> 5.      What is the meaning of a signal in this context?

Means a POSIX signal, like SIGINT.

> 6.      Why is the name 'sig' not appearing in the usage shown above. Or why is it they talk only about thread-id only?

Because the usage lists "action", whose definition gets expanded below.

> 8.      I hope the C sig & S sig are still a supported

I'm not sure I understand this last question.

> If there is a web site where these kind of questions have been answered please point me to it.

[I am not answering all questions from this message.]

The GDB documentation should answer your questions; if it does not, then
you can submit a patch improving it (please, do so!).  Also, an obvious
good source of documentation is the source code itself.  I answered some
of those questions in private (in reply to your message), and pointed
you to some functions that you might be interested in reading.

Cheers,

-- 
Sergio
GPG key ID: 65FC5E36
Please send encrypted e-mail if possible
http://blog.sergiodj.net/


      reply	other threads:[~2014-06-09 23:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-09 17:40 Vardhana, Ananda
2014-06-09 23:26 ` Sergio Durigan Junior [this message]

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=m34mzt7jhm.fsf@redhat.com \
    --to=sergiodj@redhat.com \
    --cc=ananda.vardhana@intel.com \
    --cc=gdb@sourceware.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