This is the mail archive of the
gdb@sourceware.org
mailing list for the GDB project.
Re: Questions on vCont
- From: Sergio Durigan Junior <sergiodj at redhat dot com>
- To: "Vardhana\, Ananda" <ananda dot vardhana at intel dot com>
- Cc: "gdb\ at sourceware dot org" <gdb at sourceware dot org>
- Date: Mon, 09 Jun 2014 20:26:13 -0300
- Subject: Re: Questions on vCont
- Authentication-results: sourceware.org; auth=none
- References: <301B88517A226B4DA3D210EF3D49753273F76D16 at ORSMSX102 dot amr dot corp dot intel dot com>
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/