LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Jason Wessel <jason.wessel@windriver.com>
Cc: Jan Kiszka <jan.kiszka@web.de>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	kgdb-bugreport@lists.sourceforge.net,
	Thomas Gleixner <tglx@linutronix.de>,
	"H. Peter Anvin" <hpa@zytor.com>
Subject: Re: [PATCH 1/3] KGDB: Major refactoring
Date: Thu, 7 Feb 2008 13:13:43 +0100	[thread overview]
Message-ID: <20080207121343.GA5697@elte.hu> (raw)
In-Reply-To: <47AA5165.4070201@windriver.com>


* Jason Wessel <jason.wessel@windriver.com> wrote:

> > Could you try something else too perhaps, which would be way useful 
> > for me: to add a sysctl flag (or something like that) to change 
> > kgdboc to accept a Ctrl-C and break into kgdb mode? [this means a 
> > simple Ctrl-C on a kgdboc line would break into KGDB as well - but 
> > that would be an acceptable price.] Right now kgdboc just hangs when 
> > gdb attaches - i have to generate a SysRq sequence via a terminal 
> > emulator to break it into KGDB mode.
> 
> FYI, even if you were to hack in a control-c vs sysrq, gdb will still 
> hang on connect because it does not issue a break of any kind when it 
> connects.  It assumes the connection is in a usable state.

sigh. That's quite a usability barrier IMHO.

> The proxy spliter automatically sends the break (or in the current 
> case the sysrq g)

any link to the proxy splitter? Googling for "kgdb proxy splitter" did 
not yield anything obviously on-topic.

	Ingo

      parent reply	other threads:[~2008-02-07 12:14 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-05 23:34 Jan Kiszka
2008-02-05 23:44 ` Maxim Levitsky
2008-02-06  4:40 ` Jason Wessel
2008-02-07  0:13 ` Ingo Molnar
2008-02-07  0:31   ` Jason Wessel
2008-02-07  7:47     ` Jan Kiszka
2008-02-07 12:13     ` Ingo Molnar [this message]

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=20080207121343.GA5697@elte.hu \
    --to=mingo@elte.hu \
    --cc=hpa@zytor.com \
    --cc=jan.kiszka@web.de \
    --cc=jason.wessel@windriver.com \
    --cc=kgdb-bugreport@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tglx@linutronix.de \
    --subject='Re: [PATCH 1/3] KGDB: Major refactoring' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).