On Mon, Apr 04, 2005 at 07:46:33PM +0200, Blaisorblade wrote:
> > CONFIG_PT_PROXY=y
> Maybe you could try disabling this, and saying if it makes a difference. It's
> the only piece of code which could hide such a bug, but still this code
> shouldn't be running since it's for TT mode only.
bingo.
> > . a lot of SIGTRAP here
> This is strange.
> > . until i wrote:
i have the same problem, with the same symptoms. However, im not using
skas mode, only TT.
this happens to me whenever i try to debug a uml kernel newer than
2.6.6 .
when uml is started with "debug", the gdb consol
On Monday 04 April 2005 13:55, marco ghidinelli wrote:
> hello,
>
> i'm trying to debug a kernel with the skas patches, but it doesn't work:
What you see below is very strange, never seen yet by me and not reproducible
(it works ok for me, I just retested).
> the uml-kernel is a vanilla 2.6.11.6.
On Mon, Apr 04, 2005 at 01:47:02PM -0400, Jeff Dike wrote:
> On Mon, Apr 04, 2005 at 01:55:58PM +0200, marco ghidinelli wrote:
> > Program received signal SIGTRAP, Trace/breakpoint trap.
> > 0xa0010005 in _start () at proc_fs.h:159
> > 159 res->data=data;
> > (gdb)
> >
> > ...
On Mon, Apr 04, 2005 at 01:55:58PM +0200, marco ghidinelli wrote:
> Program received signal SIGTRAP, Trace/breakpoint trap.
> 0xa0010005 in _start () at proc_fs.h:159
> 159 res->data=data;
> (gdb)
>
> . a lot of SIGTRAP here
There should only be a single SIGTRAP, when
hello,
i'm trying to debug a kernel with the skas patches, but it doesn't work:
the uml-kernel is a vanilla 2.6.11.6.
the host kernel is a vanilla 2.6.11.6 with the -skas3-v8-rc5 patch.
$ gdb linux
GNU gdb 6.3-debian
(gdb) r
Starting program: /home/marcogh/linux-uml/linux
Program received si