[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Thu, 1 Jan 2009 06:46:41 -0800
From: Daniel Phillips <phillips@...nq.net>
To: tux3@...3.org
Cc: linux-fsdevel@...r.kernel.org, Jeff Dike <jdike@...toit.com>,
Dave Chinner <david@...morbit.com>, sniper <s3c24xx@...il.com>,
linux-kernel@...r.kernel.org
Subject: Re: [Tux3] Tux3 report: A Golden Copy
On Thursday 01 January 2009 01:56, Daniel Phillips wrote:
> On Wednesday 31 December 2008 10:14, sniper wrote:
> > Sorry I meet another problem. After the system was completely setupped,
> > the gdb interface will be covered with that system interaction interface.
> > So, I can't stop the system's running and add some new break point etc.
> > But I can do those operations in remote kgdb debugging.
> >
> > Any method to fix this problem?
> >
> > Thanks.
>
> I haven't figured that one out...
...and now I have. From Jeff's docs:
debian package: user-mode-linux-doc
file:///usr/share/doc/user-mode-linux-doc/html/debugging-skas.html
"If you need to interrupt UML, you can't ^C it because the terminal
is in raw mode, and the ^C will just hit whatever UML is running.
What you need to do is send the UML kernel thread a SIGINT from
another shell. It is normally the first process after the gdb"
I take no responsibility for the following command:
kill -INT $(pgrep linux | head -n1)
Regards,
Daniel
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists