Followed the differences found by Qian and verified none of them (did
not verify the ppc suspicious one) has any regression in GDB testsuite.
I did not reproduce the original possible regression seen on ppc64 RHEL6
systems. The kernel was build directly from roland's git tree with and without
On Mon, 2009-11-30 at 17:33 +0530, Srikar Dronamraju wrote:
This patch implements an in-kernel gdb stub.
It provides an interface between gdb and Linux Kernel by implementing
the remote serial protocol. This gdbstub uses utrace infrastructure.
This patch provides register set access, signal
* Peter Zijlstra pet...@infradead.org [2009-11-30 13:09:12]:
On Mon, 2009-11-30 at 17:33 +0530, Srikar Dronamraju wrote:
This patch implements an in-kernel gdb stub.
It provides an interface between gdb and Linux Kernel by implementing
the remote serial protocol. This gdbstub uses utrace
On Mon, 2009-11-30 at 18:02 +0530, Srikar Dronamraju wrote:
* Peter Zijlstra pet...@infradead.org [2009-11-30 13:09:12]:
On Mon, 2009-11-30 at 17:33 +0530, Srikar Dronamraju wrote:
This patch implements an in-kernel gdb stub.
It provides an interface between gdb and Linux Kernel by
* Peter Zijlstra pet...@infradead.org [2009-11-30 13:41:47]:
This is a In-kernel gdbstub to debug user space programs.
This stub doesnt help in debugging kernel.
Hence I am not sure how to compare kgdb gdbstub with this gdbstub.
Can you please provide more pointers on what you were
On Mon, 2009-11-30 at 18:49 +0530, Srikar Dronamraju wrote:
This is suppose to be one of the interfaces to use utrace, i.e Allow
gdb to use utrace features without having to change gdb itself.
Though there are not enough features in this patch, intentions include
support multi-threaded
I guess Christoph, Roland and Frank would be able to explain in a better
fashion the rational and advantages of this stub over convential gdb.
Hmm,. wouldn't it make much more sense to extend the current kgdb stub
to include userspace debugging, providing an all-in-one solution?
I see
peterz wrote:
Hmm,. wouldn't it make much more sense to extend the current kgdb stub
to include userspace debugging, providing an all-in-one solution?
I think it would be much more powerful to be able to observe the full
software stack and not be limited by this user-kernel barrier.
There
* Frank Ch. Eigler f...@redhat.com wrote:
peterz wrote:
Hmm,. wouldn't it make much more sense to extend the current kgdb stub
to include userspace debugging, providing an all-in-one solution?
I think it would be much more powerful to be able to observe the full
software stack and
On Mon, Nov 30, 2009 at 04:16:50PM +0100, Ingo Molnar wrote:
[...]
kgdb exists here and today in the kernel and you cannot just build a
facility that doesnt replace it and doesnt integrate well with it.
Surely you don't mean that: every non-kgdb facility in the kernel
meets that definition,
On 11/29, Roland McGrath wrote:
Please file this test case on bugzilla.redhat.com for Fedora 12 glibc.
https://bugzilla.redhat.com/show_bug.cgi?id=542731
Oleg.
On 11/30, Benjamin Herrenschmidt wrote:
On Mon, 2009-11-30 at 10:15 +1100, Benjamin Herrenschmidt wrote:
Yes, the asm should be changed. I suppose we could check if the result
of do_syscall_trace_enter is negative, and if it is, branch to the exit
path using r3 as the error code. Would
On 11/30, Benjamin Herrenschmidt wrote:
On Sun, 2009-11-29 at 22:07 +0100, Oleg Nesterov wrote:
If I change the test-case to use NEWVAL == 1000 (or any other value
greater than NR_syscalls), then the tracee sees ENOSYS and this is
correct too.
But I do not see how it is possible to
Title: Untitled Document
Coolgift é a nova marca de packs-oferta de experiências da Lifecooler.
Doze gamas de vários temas de lazer, para todas as ocasiões e a preços
muito acessíveis.
Gamas COOLGIFT
4 Patas O melhor para os
14 matches
Mail list logo