Skip to contentSkip to conversation

i386: fix one case of stuck dwarf2 unwinder II

PATCH Chuck Ebbert 2 participants 2 messages Aug 6, 2006

lore
Share & tools
lore
#0 lore raw

In-Reply-To: <[email protected]>

Quoted 4 lines · Andi Kleen

Hmm, actually I applied it but then I had doubts it actually works -- I think you don't need _stext but the code before the first call in head. Since head.S doesn't do a call that's probably start_kernel

But head.S does do a call (on i386 but not x86_64 AFAICT):

| #ifdef CONFIG_SMP
|        movb ready, %cl
|        movb $1, ready
|        cmpb $0,%cl
|        je 1f                   # the first CPU calls start_kernel
|                                # all other CPUs call initialize_secondary
|        call initialize_secondary
|        jmp L6
| 1:
| #endif /* CONFIG_SMP */
|        call start_kernel
| L6:
|        jmp L6                  # main should never return here, but
|                                # just in case, we know what happens.

And the backtraces I saw ended up at L6:

| DWARF2 unwinder stuck at 0xc0100210

System.map on i386 SMP says:

| c0100210 t L6

Signature · 1 line
Chuck
#1 lore raw
Quoted 8 lines

And the backtraces I saw ended up at L6:

| DWARF2 unwinder stuck at 0xc0100210

System.map on i386 SMP says:

| c0100210 t L6

Yes that's the problem. If you check for <= stext/_stext then the unwinder won't catch the L6 (which is above it) and report a "stuck" again

-Andi