Skip to content
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

cmd/link: occasional failures with "unreachable sym in relocation" since 2021-09-12 #49752

Open
bcmills opened this issue Nov 23, 2021 · 6 comments
Open

Comments

@bcmills
Copy link
Member

@bcmills bcmills commented Nov 23, 2021

greplogs --dashboard -md -l -e ': unreachable sym in relocation: '

2021-11-22T23:00:32-0244343/freebsd-amd64-13_0
2021-11-19T21:57:03-6027b21/freebsd-amd64-13_0
2021-11-16T19:18:26-8122e49-6c36c33/freebsd-amd64-12_2
2021-09-12T01:06:53-0d8a4bf/linux-riscv64-unmatched

CC @cherrymui @thanm

@bcmills
Copy link
Member Author

@bcmills bcmills commented Nov 23, 2021

These failures started within the 1.18 cycle, so marking as release-blocker to determine whether this is a regression (and whether it may affect other platforms too).

Loading

@cherrymui
Copy link
Contributor

@cherrymui cherrymui commented Nov 23, 2021

These failures look weird, especially being nondeterministic. Maybe it is due to memory corruption somewhere?

Loading

@thanm
Copy link
Contributor

@thanm thanm commented Nov 23, 2021

Not really sure what to do with this bug, given the failure mode. Normally I would lease a builder and run some test or set of tests in a loop to try to reproduce -- in this case, even if I were able to reproduce it a few times, what then? I don't see any commonality in terms of the symbols that are suddenly being switched from reachable to unreachable.

Loading

@bcmills
Copy link
Member Author

@bcmills bcmills commented Nov 23, 2021

Maybe it is due to memory corruption somewhere?

“possible memory corruption on FreeBSD” is #46272, open since May. 😩

Still, it seems odd to me that this particular failure mode doesn't show up in the logs until recently. Maybe the memory corruption has a non-trivial interaction with the 1.18 GC changes? (Perhaps the corruption is triggered by having the GC active during some step of the linking process?)

Loading

@thanm
Copy link
Contributor

@thanm thanm commented Nov 23, 2021

Just out of curiosity, how far back does "greplogs" go? What's the oldest log that it will fetch?

Loading

@bcmills
Copy link
Member Author

@bcmills bcmills commented Nov 23, 2021

Depends on what you've downloaded with fetchlogs. (It looks like the semi-arbitrary cutoff for my database for the main repo is currently 2019-06-06.)

Loading

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
3 participants