------- =_aaaaaaaaaa0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <524.804639990.1@gandalf.sigmasoft.com>

> > I just added PT_READ_U and PT_WRITE_U from infptrace.c into
> > /usr/include/sys/ptrace.h, and it built. Is ptrace.h on NetBSD
> > obsolete?
> 
> PT_READ_U and PT_WRITE_U are the 'old way' of getting and setting
> process registers.  not particularly 'clean,' nor particularly secure.
>
> the new way is with PT_GETREGS and PT_SETREGS (and PT_{GET,SET}FPREGS).

Agreed.  But you still need PT_{READ,WRITE}_U to deal with signal
handlers and stuff, no?

> Adding PT_READ_U and PT_WRITE_U to ptrace.h won't help; nothing will
> actually be implementing them, anyway.

But perhaps they should be implemented?

> you should change infptrace.c to use the new functions.  (If you do
> so, you might mail the list with a copy of the diffs.)

What functions are there to see which signal handlers a traced process
have installed?  How can a debugger detect wether or not a signal has
occured?

Thorsten

------- =_aaaaaaaaaa0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <524.804639990.2@gandalf.sigmasoft.com>
Content-Description: Signature

--
Thorsten Lockert        | postmaster@sigmasoft.com | Universe, n.:
1262 Golden Gate Avenue | hostmaster@sigmasoft.com |         The problem.
San Francisco, CA 94115 | tholo@sigmasoft.com      |

------- =_aaaaaaaaaa0--