Hi,
> On Wed, 19 Nov 2003 22:30:44 + (UTC)
> [EMAIL PROTECTED] ("Bjoern A. Zeeb") said:
db> trace
bzeeb-lists> key_cmpspidx_withmask(deadc0de,c9b5c914) at key_cmpspidx_withmask+0x2c
bzeeb-lists> key_allocsp(0,c9b5c914,2,16000210,c1426f0a) at key_allocsp+0x8b
Thank you for your report
On Wed, 19 Nov 2003, Robert Watson wrote:
> You should still be able to turn the bad instruction pointer into at least
> a function name using nm on your compiled kernel. Run nm on the kernel
> binary, and search through it until you find the symbols just before
> (lower) and just after (higher)
On Wed, 19 Nov 2003, Robert Watson wrote:
Hi,
> You should still be able to turn the bad instruction pointer into at least
> a function name using nm on your compiled kernel. Run nm on the kernel
> binary, and search through it until you find the symbols just before
> (lower) and just after (hig
On Wed, 19 Nov 2003, Bjoern A. Zeeb wrote:
> I am regularly getting those but unfortunately I neither have DDB in
> that kernel nor can get a crash dump nor do I have built wie DEBUG=-g.
>
> Is there anything more I can do apart from rebuilding kernel with
> support of all the missing debugging
Hi,
I am regularly getting those but unfortunately I neither have DDB in that
kernel nor can get a crash dump nor do I have built wie DEBUG=-g.
Is there anything more I can do apart from rebuilding kernel with support
of all the missing debugging flags (which is in progress) ?
I am logged in via
