kdb
[Top] [All Lists]

Re: [PATCH] oops on entry to kdb with gcc 3.1

To: jim.houston@xxxxxxxxx
Subject: Re: [PATCH] oops on entry to kdb with gcc 3.1
From: Keith Owens <kaos@xxxxxxx>
Date: Thu, 01 Aug 2002 22:46:27 +1000
Cc: kdb@xxxxxxxxxxx
In-reply-to: Your message of "Thu, 01 Aug 2002 07:20:36 -0400." <200208011120.g71BKaL01887@linux.local>
Sender: owner-kdb@xxxxxxxxxxx
On Thu, 1 Aug 2002 07:20:36 -0400, 
Jim Houston <jim.houston@xxxxxxxxx> wrote:
>Compiling the kdb with gcc 3.1 breaks kdba_setjmp.  It seems
>that gcc 3.1 is more clever about omiting frame pointers for 
>leaf functions.  When it does this for kdba_setjmp it causes an
>oops on entry to kdb.
>
>The attached patch uses the gcc built in functions to get the
>frame pointer and the return adddress.  This gets rid of the hard
>coded stack offsets and should make it more portable.

Does __builtin_frame_address work for older gcc, even if you compile
the kernel without frame pointers?  I vaguely remember that it returns
garbage on older versions of gcc if ebp is not dedicated.


<Prev in Thread] Current Thread [Next in Thread>