From: Arjan van de Ven <arjan@infradead.org>
To: Tigran Aivazian <tigran@veritas.com>
Cc: "H. Peter Anvin" <hpa@zytor.com>, Andi Kleen <ak@muc.de>,
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: Tue, 18 Jan 2005 12:51:00 +0100 [thread overview]
Message-ID: <1106049060.6307.73.camel@laptopd505.fenrus.org> (raw)
In-Reply-To: <Pine.LNX.4.61.0501181112120.2911@ezer.homenet>
On Tue, 2005-01-18 at 11:25 +0000, Tigran Aivazian wrote:
> However, this highlighted a more serious problem in the x86_64 kernel (or
> more likely in the kdb patch) --- the kernel compiled with -g panics when
> you try to return from kdb after hitting a breakpoint. This is a bug and
> I'll investigate to find out the reason why it panics. (I hope it is not
> an "assumption" of the x86_64 port that one must never compile the kernel
> with -g either...)
That is isn't; for example the Fedora Core 2 and 3 and the Red Hat
Enterprise Linux 4 kernels are compiled wit -g.
next prev parent reply other threads:[~2005-01-18 11:51 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-14 16:34 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
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 [this message]
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=1106049060.6307.73.camel@laptopd505.fenrus.org \
--to=arjan@infradead.org \
--cc=ak@muc.de \
--cc=hpa@zytor.com \
--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
all inboxes | Powered by JetHome®