From: "H. Peter Anvin" <hpa@zytor.com>
To: Tigran Aivazian <tigran@veritas.com>
Cc: Arjan van de Ven <arjan@infradead.org>, Jan Hubicka <jh@suse.cz>,
Jack F Vogel <jfv@bluesong.net>,
linux-kernel@vger.kernel.org, Linus Torvalds <torvalds@osdl.org>
Subject: Re: [discuss] booting a kernel compiled with -mregparm=0
Date: Mon, 17 Jan 2005 10:10:15 -0800 [thread overview]
Message-ID: <41EBFF87.6080105@zytor.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0501171002190.4644@ezer.homenet>
Tigran Aivazian wrote:
> On Mon, 17 Jan 2005, Arjan van de Ven wrote:
>
>>> Actually, having cc'd Linus made me think very _carefully_ about what I
>>> say and I went and checked how the userspace does it, as I couldn't
>>> believe that such fine piece of software as gdb would be broken as well.
>>> And to my surprize I discovered that gdb (when a program is compiled
>>> with
>>> -g) works fine! I.e. it shows the function arguments correctly. And
>>
>> so why don't you use kgdb instead of kdb ?
>
> If kdb was some dead unmaintained piece of software then, yes, I would
> follow your advice and switch to kgdb. But kdb is a very nice and
> actively maintained piece of work, so it should be fixed to show the
> parameter values correctly in the backtrace.
That's a kdb maintainer issue. The x86-64 folks have nicely provided a
set of libraries to do backtraces, etc. Your previous rant is just so
far off base it's not even funny.
-hpa
next prev parent reply other threads:[~2005-01-17 18:15 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-14 16:34 booting a kernel compiled with -mregparm=0 Tigran Aivazian
2005-01-14 20:56 ` [discuss] " Jan Hubicka
2005-01-14 21:28 ` linux-os
2005-01-15 2:29 ` H. Peter Anvin
2005-01-17 9:30 ` Tigran Aivazian
2005-01-17 9:53 ` Arjan van de Ven
2005-01-17 10:04 ` Tigran Aivazian
2005-01-17 18:10 ` H. Peter Anvin [this message]
2005-01-17 20:22 ` Andi Kleen
2005-01-17 20:38 ` H. Peter Anvin
2005-01-17 22:08 ` Andi Kleen
2005-01-18 11:25 ` Tigran Aivazian
2005-01-18 11:51 ` Arjan van de Ven
2005-01-18 13:04 ` Tigran Aivazian
2005-01-18 13:16 ` Tigran Aivazian
2005-01-17 10:59 ` Andi Kleen
2005-01-17 13:17 ` Tigran Aivazian
2005-01-17 16:38 ` Linus Torvalds
2005-01-18 20:38 ` Keith Owens
2005-01-18 23:15 ` Andi Kleen
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=41EBFF87.6080105@zytor.com \
--to=hpa@zytor.com \
--cc=arjan@infradead.org \
--cc=jfv@bluesong.net \
--cc=jh@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=tigran@veritas.com \
--cc=torvalds@osdl.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