-
-
Notifications
You must be signed in to change notification settings - Fork 482
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Building firejail fbuilder creates 2 rodata sections and the data does not make valgrind happy. #118
Comments
In ELF, section names are not significant, so it is okay to create multiple sections with the same name. So, technically, this is a valgrind's issue. That being said, it isn't too hard for mold to not create multiple .rodata sections, so I'll make such change. |
With the above change, mold now creates .rodata.cst and .rodata.str instead of .rodata. Could you verify whether or not the above change fixes your problem? |
I am really not sure why the sandbox was running and is currently not running, but the output is identical now with and without mold.
|
I was trying to figure out the error source in fbuild, when I realized that mold creates two .rodata sections as you can see in the bug report. Using the regular linker does only create one .rodata section.
I think this makes valgrind very unhappy and it also looks abit odd.
Is this a bug of valgrind or is there some specification of how many identically named sections (or inspecial .rodata sections) may exist? Or is this some gcc shennanigan?
gdb starts fine, so I guess it has no problems with symbol lookup.
Reproducing instructions:
The text was updated successfully, but these errors were encountered: