[Bug 227093] powerpc64/pseries: Symbol table not relocated

[email protected]
Newsgroups gmane.os.freebsd.devel.ppc
Message-ID <[email protected]/bugzilla/>
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227093

Breno Leitao <[email protected]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|patch                       |

--- Comment #2 from Breno Leitao <[email protected]> ---
Hi Nathan,

This patch shouldn't be considered to be applied. This is just a first
demonstration on how to solve this issue in a hackish way. We definitely need
to fix the debug symbol table.

Regarding your proposal, it didn't help either, since I still see the following
stack when I run [1]

0xe000000000318da0: at 0xc00000000067bd4c
0xe000000000318ed0: at .dump+0x2c
0xe000000000318f50: at .handler+0x3c
0xe000000000318fd0: at 0xc0000000006001e8
0xe000000000319070: at 0xc0000000005f1d60
0xe000000000319450: at 0xc0000000005f2588
0xe000000000319510: at 0xc0000000005f26f4
0xe0000000003195b0: at 0xc0000000009ca550
0xe000000000319770: at 0xc0000000009bf418
0xe000000000319810: user SC trap by 0x8100daef8: srr1=0x800000000000f032
            r1=0x3fffffffffffbd90 cr=0x44224044 xer=0x20000000 ctr=0x8100daef0
r2=0x810258e50

Looking further at the code, it seems that the linker_kernel_file->address is
not affecting the debug symbols st_value field at all, that explains why they
are not being relocated.

For now, I am trying to relocate the whole debug symbol table manually to see
if that fixes the problem.


[1] https://github.com/leitao/freebsd_modules/tree/master/dump_stack

-- 
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
[email protected] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ppc
To unsubscribe, send any mail to "[email protected]"
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.