> On Jun 22, 2016, at 3:38 AM, John Otter wrote:
>
>> "I want a GDB server port for user space process 123"
>
> How would I start this gdb server? Do you mean a gdb-server running in
> the target userspace? Wouldn't that make impossible to use it when the
> kernel is stopped?
No, the python sc
> "I want a GDB server port for user space process 123"
How would I start this gdb server? Do you mean a gdb-server running in
the target userspace? Wouldn't that make impossible to use it when the
kernel is stopped?
I tried searching around and the only resources I found is this old
macros file
The right way to do this is to say "I want a GDB server port for user space
process 123". The python would then start up a socket that can be connected to
that can vend the information about the user space process directly through a
dedicated GDB server port. Memory reads would translate the mem
I'm using lldb to debug the OS X kernel, and it works great.
I would like to have more flexibility in analysing user programs while
debugging the kernel itself,
and specifically symbolicate the code of the user programs.
For example I often use the command showthreaduserstack defined here
http://o
