Re: [0/2] Inspect extra signal information

[Mark Kettenis <mark.kettenis@xs4all.nl>]

> From: Pedro Alves <pedro@codesourcery.com>
> Date: Mon, 12 Jan 2009 18:46:51 +0000
> 
> Hi!
> 
> This mini series adds support for inspecting extra signal information.
> 
> What this means is, we get a new $_siginfo convenience variable that
> is typed to look like the siginfo_t object on unix-ish platforms (but
> can be any other type appropriate for the target platform).

This looks pretty cool.  I've often wished I had this information
available.  And I've also wondered about a resonable way to present it
to the user.  Your approach seems very reasonable to me.  I can't
really comment on the infrastructure to build these "computed values".
But the target-sepcific support stuff seems reasonable to me. 

One thing I wonder about is whether it really is a good idea to is the
obfuscated typenames like __uid_t instead of a straight uid_t.  I
realize that is the way the type is defined in headers, but in GDB we
don't really have to worry about namespace pollution.

The other thing I worry about is padding for these structure types
that may be necessary on some platforms.  Does your code handle that?