This is the mail archive of the gdb-patches@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: [PATCH 3/5] s/struct process_info/struct inferior/


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 (éå)


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