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

Broken adress_sanitizer in gcc10.3 (+durty patch) #102

Open
sleeperss opened this issue Apr 29, 2022 · 1 comment
Open

Broken adress_sanitizer in gcc10.3 (+durty patch) #102

sleeperss opened this issue Apr 29, 2022 · 1 comment
Assignees
Labels
Bug 🐛 Error, flaw or fault Need Testing 🧪 Issue/PR must be tested before concluding. PR welcomed 💡 Related Pull Requests are welcomed for this issue!
Milestone

Comments

@sleeperss
Copy link

sleeperss commented Apr 29, 2022

Hi,

When cross-compilling with the address sanitizer for bulleyes I get the following error at link time :
/opt/cross/tools/bin/../lib/gcc/aarch64-linux-gnu/10.3.0/../../../../aarch64-linux-gnu/bin/ld: program_name: hidden symbol `__aarch64_ldadd8_acq_rel' in /opt/cross/tools/bin/../lib/gcc/aarch64-linux-gnu/10.3.0/libgcc.a(ldadd_8_4.o) is referenced by DSO

It seems to be an error from gcc-10 as mentionned in https://lists.freebsd.org/archives/freebsd-ports/2021-July/000431.html

I got it to work by replacing gcc-10.3.0 with gcc-10.3.1 and (I don't know why, possibly a libc dependency problem) removing the lines 1642 to 1649 of c++/10.3.1/aarch64-linux-gnu/bits/c++config.h.

Without the last modification I get multiple error like :

error: there are no arguments to 'pthread_rwlock_clockrdlock' that depend on a template parameter
error: 'pthread_mutex_clocklock' was not declared in this scope; did you mean 'pthread_mutex_unlock'```

@abhiTronix abhiTronix added Bug 🐛 Error, flaw or fault PR welcomed 💡 Related Pull Requests are welcomed for this issue! Need Testing 🧪 Issue/PR must be tested before concluding. labels Apr 30, 2022
@abhiTronix abhiTronix self-assigned this Apr 30, 2022
@abhiTronix abhiTronix added this to the v3.1.0 milestone Apr 30, 2022
@abhiTronix
Copy link
Owner

@sleeperss Thanks I'll look into this and make necessary changes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug 🐛 Error, flaw or fault Need Testing 🧪 Issue/PR must be tested before concluding. PR welcomed 💡 Related Pull Requests are welcomed for this issue!
Projects
None yet
Development

No branches or pull requests

2 participants