[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Thu, 1 Jan 2009 01:56:02 -0800
From: Daniel Phillips <phillips@...nq.net>
To: tux3@...3.org
Cc: sniper <s3c24xx@...il.com>, linux-fsdevel@...r.kernel.org,
Jeff Dike <jdike@...toit.com>,
Dave Chinner <david@...morbit.com>,
linux-kernel@...r.kernel.org
Subject: Re: [Tux3] Tux3 report: A Golden Copy
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. Usually I get into gdb from uml by
setting a breakpoint, fielding a crash, or executing an explicit
breakpoint: asm("int3"). But I have been unsuccessful so far in
breaking a running uml into the debugger from outside, ever since
SKAS arrived.
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