I seem to understand the problem(s). I am a bit surprized. Basically
I have the questions about almost every utrace_ function. I'll try
to recheck and summarize my concerns tomorrow with a fresh head, I
hope I missed something.
Ok. That stuff about pure kernel implementation issues doesn't
oleg wrote:
[...]
- It doesn't support all-stop mode.
Please tell me if this is needed. I hope not, this needs
a lot of nasty complications :/
[...]
As opposed to non-stop mode? I'm pretty sure all-stop will be needed
as that is the common default gdb usage model.
On 08/11, Tom Tromey wrote:
Oleg == Oleg Nesterov o...@redhat.com writes:
Oleg So, the patch below fixes the problem, and gdb + /proc/ugdb seems
Oleg to work.
Oleg Indeed, gdb sees that this fd is not pipe/tcp and uses the hardwire
Oleg serial_ops, but hardwire_readchar() doesn't play
Indeed, gdb sees that this fd is not pipe/tcp and uses the hardwire
serial_ops, but hardwire_readchar() doesn't play well with select().
Please teach gdb to use poll/select ?
If it makes it easier, could use:
bash$ nc -l -U /tmp/socket /proc/ugdb
(gdb) target remote |nc -U
Please see the attached ugdb.c.
It supports multiple inferiors/threads, stop/cont, clone/exit.
It doesn't report W/X when the process exits yet, but this is
only because I'd like to discuss the current problems with the
exited leader first, then implement this as a separate change.
Any code
