lkml.org 
[lkml]   [2005]   [Jan]   [18]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [discuss] booting a kernel compiled with -mregparm=0
On Mon, 17 Jan 2005, H. Peter Anvin wrote:
> Or does kdb not have a client at all? (If so, I have no sympathy for it.)

Peter, it was very easy for you to call my emails "rants" and "not even
funny" but the above statement is displaying complete ignorance of what
kdb actually is :) So, instead of "patronizing" your fellow-hacker, please
listen to what he has to say below:

I already solved this paricular problem. And the solution is (but don't
tell me you knew it, for then why didn't you tell anyone) simply ---
compile the kernel with -g and that includes enough debug information to
be able to decode the stack content correctly. And yes, kdb does show the
correct argument values now. No changes to kdb are necessary and no need
to do the work with dwarf2 implementation etc etc.

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...)

Kind regards
Tigran
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 14:09    [W:0.689 / U:0.056 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site