>> > Hi,
>> >
>> > something really bad happened (the processor jumped into hyperspace);
>> > however it looks like automatic symbol resolving isn't working;
>> > could you check if CONFIG_KALLSYMS is enabled in your kernel config?
>> > With that enabled, debugability tends to go up bigtime since at least
>> > the backtrace becomes human readable...
>>
>> I have:
>>
>> CONFIG_KALLSYMS=y
>
>Hoi,
>
>hmmmmm then something really bad happened, so bad that even the
>backtrace is corrupted ;(
How about adding this one?
CONFIG_FRAME_POINTER=y
Compiling things without frame pointer on
userspace (yes, userspace) makes debugging impossible, I wonder how the
kernel can do it without FPs.
And if you got time on your hands
CONFIG_UNWIND_INFO=y
Jan Engelhardt
--
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
