All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Phillips <phillips@phunq.net>
To: tux3@tux3.org
Cc: linux-fsdevel@vger.kernel.org, Jeff Dike <jdike@addtoit.com>,
	Dave Chinner <david@fromorbit.com>, sniper <s3c24xx@gmail.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [Tux3] Tux3 report: A Golden Copy
Date: Thu, 1 Jan 2009 06:46:41 -0800	[thread overview]
Message-ID: <200901010646.41602.phillips@phunq.net> (raw)
In-Reply-To: <200901010156.03279.phillips@phunq.net>

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

  reply	other threads:[~2009-01-01 14:46 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-31  3:35 Tux3 report: A Golden Copy Daniel Phillips
2008-12-31  3:35 ` Daniel Phillips
2008-12-31  7:34 ` sniper
2008-12-31  8:00   ` [Tux3] " Daniel Phillips
2008-12-31  8:14     ` Justin P. Mattock
2008-12-31 10:09       ` Martin Steigerwald
2008-12-31 17:41         ` Justin P. Mattock
2008-12-31 17:41           ` Justin P. Mattock
2009-01-02 20:17           ` [Tux3] " Martin Steigerwald
2009-01-02 20:36             ` Justin P. Mattock
2009-01-02 20:36               ` Justin P. Mattock
2009-01-02 22:45             ` [Tux3] " Daniel Phillips
2009-01-02 23:11               ` Justin P. Mattock
2009-01-03  1:19                 ` Daniel Phillips
2009-01-03  1:19                   ` Daniel Phillips
2009-01-03  1:32                   ` [Tux3] " Justin P. Mattock
2009-01-03  1:32                     ` Justin P. Mattock
2009-01-03  3:03                     ` [Tux3] " Daniel Phillips
2009-01-03  3:39                       ` Justin P. Mattock
2009-01-04  3:17                         ` Jamie Lokier
2009-01-04  4:15                           ` Daniel Phillips
2009-01-04  4:29                           ` Justin P. Mattock
2009-01-04 13:04                           ` Theodore Tso
2009-01-05  1:10                             ` Daniel Phillips
2009-01-05  2:13                               ` Jamie Lokier
2009-01-08  2:50                                 ` Daniel Phillips
2009-01-08  4:38                                   ` Evgeniy Polyakov
2008-12-31  8:16     ` sniper
2008-12-31  8:31     ` Dave Chinner
2008-12-31  9:40       ` Daniel Phillips
2008-12-31 14:26         ` Andi Kleen
2008-12-31 18:14         ` sniper
2008-12-31 18:18           ` sniper
2008-12-31 18:18             ` sniper
2009-01-01  9:56           ` [Tux3] " Daniel Phillips
2009-01-01 14:46             ` Daniel Phillips [this message]
2009-01-01 23:58           ` Dave Chinner

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200901010646.41602.phillips@phunq.net \
    --to=phillips@phunq.net \
    --cc=david@fromorbit.com \
    --cc=jdike@addtoit.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=s3c24xx@gmail.com \
    --cc=tux3@tux3.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.