public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Amit S. Kale" <amitkale@emsyssoft.com>
To: Tom Rini <trini@kernel.crashing.org>, Andi Kleen <ak@muc.de>
Cc: Andrew Morton <akpm@osdl.org>,
	linux-kernel@vger.kernel.org, george@mvista.com, pavel@ucw.cz
Subject: Re: kgdb for mainline kernel: core-lite [patch 1/3]
Date: Thu, 11 Mar 2004 10:27:51 +0530	[thread overview]
Message-ID: <200403111027.52534.amitkale@emsyssoft.com> (raw)
In-Reply-To: <20040310152750.GE5169@smtp.west.cox.net>

On Wednesday 10 Mar 2004 8:57 pm, Tom Rini wrote:
> On Wed, Mar 10, 2004 at 01:36:05PM +0100, Andi Kleen wrote:
> > > Yes. But as things stand, gdb 6.0 doesn't show stack traces correctly
> > > with esp and eip got from switch_to and gas 2.14 can't handle i386
> > > dwarf2 CFI. Do we want to enforce getting a CVS version of gdb _and_
> > > gas to build kgdb? Certainly not.
> >
> > binutils 2.15 should be released soon anyways AFAIK. And for x86-64 this
> > all works just fine (as demonstrated by Jim's/George's stub), so please
> > get rid of it at least for x86-64. I really don't want user_schedule
> > there, because it's completely unnecessary.
>
> I think more importantly, it's probably going to be one of those ugly
> things that will make it so much harder to get it into Linus' tree.  So
> lets just say it'll require gdb 6.1 / binutils 2.15 for KGDB to work
> best.

If we are enforcing this we need to do it correctly: is there any way to check 
from source code whether binutils version is correct (even a gas check will 
suffice)

-Amit


  reply	other threads:[~2004-03-11  4:58 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1xpyM-2Op-21@gated-at.bofh.it>
     [not found] ` <1xqXN-44F-13@gated-at.bofh.it>
     [not found]   ` <1xr7w-4c4-9@gated-at.bofh.it>
     [not found]     ` <1xrqW-4rh-51@gated-at.bofh.it>
     [not found]       ` <1xuS8-83Q-11@gated-at.bofh.it>
2004-03-08 16:57         ` kgdb for mainline kernel: core-lite [patch 1/3] Andi Kleen
2004-03-08 17:18           ` Tom Rini
2004-03-09  4:29             ` Amit S. Kale
2004-03-09  4:36           ` Amit S. Kale
2004-03-10 12:36             ` Andi Kleen
2004-03-10 15:27               ` Tom Rini
2004-03-11  4:57                 ` Amit S. Kale [this message]
2004-03-11  5:05                   ` Randy.Dunlap
2004-03-11  5:11                   ` Andi Kleen
2004-03-08  9:39 Amit S. Kale
2004-03-08  9:54 ` Andrew Morton
2004-03-08 10:15   ` Amit S. Kale
2004-03-08 10:26     ` Andrew Morton
2004-03-08 10:49       ` Amit S. Kale
2004-03-08 11:07         ` Andrew Morton
2004-03-08 11:20           ` Amit S. Kale
2004-03-08 11:44             ` Amit S. Kale
2004-03-08 11:54               ` Andrew Morton
2004-03-08 12:00                 ` Amit S. Kale
2004-03-08 15:19               ` Tom Rini
2004-03-08 22:26                 ` George Anzinger
2004-03-09  8:58                 ` Amit S. Kale
2004-03-08 22:19               ` George Anzinger
2004-03-09  5:08                 ` Amit S. Kale
2004-03-09 15:37                   ` Tom Rini
2004-03-08 11:48             ` Andrew Morton
2004-03-08 22:21               ` George Anzinger
2004-03-08 15:22             ` Tom Rini
2004-03-08 16:32               ` Amit S. Kale
2004-03-08 22:29               ` George Anzinger
2004-03-08 22:15         ` George Anzinger
2004-03-09  4:46           ` Amit S. Kale
2004-03-09  9:29         ` Amit S. Kale
2004-03-09 15:06           ` Tom Rini
2004-03-10  4:05             ` Amit S. Kale

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=200403111027.52534.amitkale@emsyssoft.com \
    --to=amitkale@emsyssoft.com \
    --cc=ak@muc.de \
    --cc=akpm@osdl.org \
    --cc=george@mvista.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@ucw.cz \
    --cc=trini@kernel.crashing.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox