From: "Amit S. Kale" <amitkale@emsyssoft.com>
To: Andi Kleen <ak@suse.de>
Cc: jim.houston@comcast.net, akpm@osdl.org,
linux-kernel@vger.kernel.org,
kgdb-bugreport@lists.sourceforge.net
Subject: Re: Fixes for .cfi directives for x86_64 kgdb
Date: Sun, 21 Mar 2004 18:42:14 +0530 [thread overview]
Message-ID: <200403211842.14885.amitkale@emsyssoft.com> (raw)
In-Reply-To: <20040319202315.3c01a501.ak@suse.de>
On Saturday 20 Mar 2004 12:53 am, Andi Kleen wrote:
> On Fri, 19 Mar 2004 18:47:43 +0530
>
> "Amit S. Kale" <amitkale@emsyssoft.com> wrote:
> > Thanks. Checked into kgdb.sourceforge.net cvs tree
>
> It's not very useful because that tree still has the broken
> "interrupt threads" support.
Does it show interrupt threads or not?
-Amit
next prev parent reply other threads:[~2004-03-21 13:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-17 21:37 Fixes for .cfi directives for x86_64 kgdb Jim Houston
2004-03-17 23:53 ` Andi Kleen
2004-03-18 16:51 ` Jim Houston
2004-03-19 13:17 ` Amit S. Kale
2004-03-19 19:23 ` Andi Kleen
2004-03-21 13:12 ` Amit S. Kale [this message]
2004-03-23 0:17 ` [PATCH]Call frame debug info for 2.6 kernel George Anzinger
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=200403211842.14885.amitkale@emsyssoft.com \
--to=amitkale@emsyssoft.com \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=jim.houston@comcast.net \
--cc=kgdb-bugreport@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.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.