Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Yao Qi <yao@codesourcery.com>
To: Pedro Alves <palves@redhat.com>
Cc: Doug Evans <dje@google.com>, <gdb-patches@sourceware.org>
Subject: Re: [PATCH 3/5] s/struct process_info/struct inferior/
Date: Wed, 21 Mar 2012 04:27:00 -0000	[thread overview]
Message-ID: <4F6958CD.30504@codesourcery.com> (raw)
In-Reply-To: <4F68C48E.5040303@redhat.com>

On 03/21/2012 01:55 AM, Pedro Alves wrote:
> An `inferior' in GDB represents an abstraction that does not exist in GDBserver.
> For example, you have the same inferior before creating the process, and
> after the process exits:
> 
>  inferior 1 -> no process
>  *start*
>  inferior 1 -> process 7450
>  *process 7450 exits*
>  inferior 1 -> no process

In terms of ITSET, there should be one created process associated with
an inferior.  For example, there are two inferiors,

  inferior 1 -> no process,
  inferior 2 -> process 1234,

When using ITSET i1-2, we don't care about inferior 1, because there is
no process created at all.

As you pointed out blew, my work doesn't cover dynamic itset.  In this
case, when process is created and associated to inferior 1 later, I
don't have a mechanism to update itset in target side.

> It doesn't seem like you'd be able to convert dynamic itsets involving inferior ids
> or gdb thread ids (which are most) retaining the dynamic-ness, which means that the
> conversion ends up only with a list of already-known objects, which results in a much
> simpler and easier to specify (and maintain forever) syntax on the target side.  There's
> also the non-id predicates, which I have on idea on how they are intended to be
> converted.

I am unable to handle dynamic itset so far.

-- 
Yao (齐尧)


  parent reply	other threads:[~2012-03-21  4:27 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-16 15:01 [PATCH 0/5] Preparatory patches for ITSET in GDBserver Yao Qi
2012-03-16 15:01 ` [PATCH 1/5] Define target_core_of_thread in gdbserver Yao Qi
2012-03-16 15:01 ` [PATCH 4/5] move server.h to inferior.h Yao Qi
2012-04-13 17:37   ` Tom Tromey
2012-03-16 15:01 ` [PATCH 3/5] s/struct process_info/struct inferior/ Yao Qi
2012-03-20 16:28   ` Doug Evans
2012-03-20 17:55     ` Pedro Alves
2012-03-20 21:31       ` Doug Evans
2012-03-21  4:27       ` Yao Qi [this message]
2012-03-21  3:18     ` Yao Qi
2012-03-16 15:02 ` [PATCH 5/5] move server.h to gdbthread.h Yao Qi
2012-04-13 17:43   ` Tom Tromey
2012-04-19  4:35     ` Yao Qi
2012-04-29  6:46       ` [committed]: " Yao Qi
2012-03-16 15:02 ` [PATCH 2/5] Move vec to common/ Yao Qi

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=4F6958CD.30504@codesourcery.com \
    --to=yao@codesourcery.com \
    --cc=dje@google.com \
    --cc=gdb-patches@sourceware.org \
    --cc=palves@redhat.com \
    /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