-
Notifications
You must be signed in to change notification settings - Fork 114
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
ASAN reported new/delete size mismatch (sliced object?) #274
Comments
This has happened to me since I started using asan. It appears to be something deep in the guts of sigc++ and not anything we can fix in our code. If you can find a proper fix/workaround then great, otherwise just use that asan env var to suppress it while looking for real bugs. |
It seems that we're hitting libsigcplusplus/libsigcplusplus#10 which is WONTFIX for sigc++ 2.x (we'd need to update to sigc++ 3.x to fix it, as the fix requires breaking ABI compat) |
So I guess we can close this issue then?
Maybe put a note in the manual about this somewhere so other devs know, then just set that asan variable for debug builds until then? |
I'll have to look and see if there's a finer-grained way to suppress this specific error... |
It looks like we'll have to use a compile-time blacklist for this error since it's coming from code in a header file... |
...and it turns out -fsanitize-blacklist is a clangism. Using ASAN_OPTIONS=new_delete_type_mismatch=false at runtime works for now, but isn't particularly desirable since that shuts off that check for our code as well. |
Closing as unfixable for now, will update to sigc++3 once all supported platforms have it available. |
I started up glscopeclient as shown below with my Rigol DS1054Z powered on, and passed it the default name, rigol for the driver, usbtmc for the transport, and /dev/usbtmc1 as the device (which is the correct device), and I get the following crash after tabbing to the OK button and hitting enter (this was with latest master as of the time of the report on Debian Bullseye, btw):
The text was updated successfully, but these errors were encountered: