In-Reply-To: <[email protected]>
On Wed, 03 May 2006 20:26:21 +0100, Andy Whitcroft wrote:
> <ffffffff8047c8e8>{__sched_text_start+1856} <EOE>new stack 0 (0 0
> 10046 10 ffffffff8047c8e8)
Wow. The extra debug patch yields... exactly the same address that's
already being printed.
The real problem is that the stack-dump code prints the wrong symbol
name here. I don't see any easy way to fix it other than to put some
filler at __sched_text_start so the first sched function has a unique
address.
--
Chuck
"Penguins don't come from next door, they come from the Antarctic!"
-
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]
