Re: [PATCH 7/8] ia64-hpux: unwinding bsp value from system call

Joel Brobecker
2010-12-28T11:35:57Z

> BZZT. Don't do that. The return of a TARGET_OBJECT_OSDATA request
> should be a table that follows the gdb/features/osdata.dtd dtd. It
> is meant as data to be fed into the "info os" command (and a non-submitted
> -info-os MI command).

Arg - I thought that using a target-specific annex name would be
sufficient.

I will use a different object kind. I could create our own object kind,
but someone it seems possible to have one that can be re-used by all
targets.

Some proposed names:

TARGET_OBJECT_OSABI_SPECIFIC_DATA
TARGET_OBJECT_OSABI_DATA
TARGET_OBJECT_TARGET_SPECIFIC_DATA
TARGET_OBJECT_TARGET_DATA

Another option is to create feature-specific objects, but then I'm
afraid the number of objects might steadily grow beyond reasonable
(I need two, right now).

The last option, is to follow the lead of some targets, and create
a CPU-specific target object: TARGET_OBJECT_IA64.

--
Joel