Re: [patch v8 05/24] frame: artificial frame id's

Jan Kratochvil
2013-12-12T19:55:40Z

On Thu, 12 Dec 2013 20:39:09 +0100, Pedro Alves wrote:
> To be more precise, the frames do have a stack, but it's <unavailable>.
> I.e., it existed, but we didn't capture it, so we can't retrieve it.
> I presume "p $sp" etc. will show <unavailable>, right?

Right.

> > To prepare for this, support frame_id's without a stack component.
>
> So special_addr will be a made up number, right? Will each such
> frame have its own special_addr ?

Yes.

> Looks like frame_ id_eq (null_frame_id, null_frame_id) now
> returns true, while it returns false before. If you discussed
> all this and came to the conclusion it's OK, please document
> it in the commit log. In any case (I'm not sure offhand if
> that's OK), the NaN comment above is no longer correct,
> and neither is this one:

That was not needed / intentional so it would be better to keep the original
behavior.

Thanks,
Jan