-
Notifications
You must be signed in to change notification settings - Fork 323
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
Wrong/misleading diagnostic in matrixmultiply==0.3.2 #2127
Comments
Usually when there is no invalidation message that means the pointer is used outside the range the tag was created for. What does the tag creation tracking message say? The "help" seems to indicate the range is big enough...
It certainly doesn't; the larger size must be coming from something else. |
The tag-tracking messages just say this:
plus a backtrace, which is in my experience not helpful when the actual retag is in a local crate. |
FWIW, what does the diagnostic look like with #2128 ? |
|
In
matrixmultiply==0.3.2
, runningI currently see this, which I find confusing:
The only tag-tracking message we get is for the tag creation. So from this I would assume that the pointer should be valid for accesses at offset 0x88, but it must not be because we have an error.
I stuck a
println!("{:?}", place)
in when the tag is created and I see this:which I think means that this is just a pointer to
f64
, so I'm really confused as to why it looks likesize_and_align_of_mplace
is coming up with a much larger size.The text was updated successfully, but these errors were encountered: