> > question for the ppc folks why does the "print symbol" magic format str
ing
> > thing print a dot symbol and not the real function name?
> > Should that be fixed instead?
>
> We have two symbols for each function, foo points to the function
> descriptor, and .foo points to the instruction
Hi Arjan,
> question for the ppc folks why does the "print symbol" magic format string
> thing print a dot symbol and not the real function name?
> Should that be fixed instead?
We have two symbols for each function, foo points to the function
descriptor, and .foo points to the instruction t
Michael Neuling wrote:
powerpc has dot symbols, so the dmesg output looks like:
<4>[0.327310] calling .migration_init+0x0/0x9c @ 1
<4>[0.327595] initcall .migration_init+0x0/0x9c returned 1 after 0 usecs
The below fixes bootgraph.pl so it handles this correctly.
question for the
powerpc has dot symbols, so the dmesg output looks like:
<4>[0.327310] calling .migration_init+0x0/0x9c @ 1
<4>[0.327595] initcall .migration_init+0x0/0x9c returned 1 after 0 usecs
The below fixes bootgraph.pl so it handles this correctly.
Signed-off-by: Michael Neuling
---
scripts
