Hello,

I have implemented the gcore command on pa-hpux for one of our customers.
I would like to contribute this work, but I know that for sure the
approach is took is not acceptable.

The work is based on using the TT_PROC_CORE ttrace command:

      TT_PROC_CORE   This request causes the traced process to generate a
                     core file in the target process's current working
                     directory. The core file is named core.pid where pid is
                     the process ID of the target process. The process's
                     state is left unchanged.  The lwpid, addr, data and
                     addr2 arguments must be zero.

So I created a new function in infttrace.c. In order to avoid re-writing
the part of gcore.c that add the command, and handles the arguments of this
command, I simply hooked the new infttrace directly into the gcore code.
A bit crude, but it works and it's pretty localized.

For the FSF tree, I'd like to implement this a little better, and it
seems to me that the core part of this command, the part that actually
creates the core file, should be a method of some vector. But which
vector?

The way the gcore command is currently written, it seems that it would
make sense for it to be part of the target vector. No?

However, in the case of HP/UX, there is a slight complication, because
the method is only good in the native case...

Any suggestion?

Attached is the infttrace function that creates the core dump. It is
largely inspired from the HP WDB debugger sources (contributed recently).

Thanks,
-- 
Joel