You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When running rustc on my repo, which has an AST parameterized over an arbitrary type T, I get:
Program received signal EXC_BAD_ACCESS, Could not access memory.
Reason: KERN_PROTECTION_FAILURE at address: 0x0000000c
0x000bb46c in glue$copy$$g14$t1$P1 ()
(gdb) bt
0 0x000bb46c in glue$copy$$g14$t1$P1 ()
1 0x003026e0 in ?? ()
Even an empty source file passed to rustc triggers the error.
The text was updated successfully, but these errors were encountered:
* handle amdgcn intrinsics
* constant addrspace is constant
* make sure we don't use constant AS for shadow
* Cleanup julia/amd
Co-authored-by: Valentin Churavy <[email protected]>
celinval
pushed a commit
to celinval/rust-dev
that referenced
this issue
Nov 29, 2024
…ng#180)
Towards rust-lang#150
### Changes
* Added a `CStr` Safety Invariant
* Added a harness for `from_bytes_until_nul`, the harness covers:
* The input slice contains a single null byte at the end;
* The input slice contains no null bytes;
* The input slice contains intermediate null bytes
### Discussion
* [Safety invariant
implementation](model-checking#150 (comment))
* [Input array
generation](model-checking#181)
### Verification Result
`./scripts/run-kani.sh --kani-args --harness ffi::c_str::verify`
```
// array size 16
Checking harness ffi::c_str::verify::check_from_bytes_until_nul...
VERIFICATION RESULT:
** 0 of 140 failed (5 unreachable)
VERIFICATION:- SUCCESSFUL
Verification Time: 7.3023376s
Complete - 1 successfully verified harnesses, 0 failures, 1 total.
```
By submitting this pull request, I confirm that my contribution is made
under the terms of the Apache 2.0 and MIT licenses.
When running
rustc
on my repo, which has an AST parameterized over an arbitrary type T, I get:Even an empty source file passed to
rustc
triggers the error.The text was updated successfully, but these errors were encountered: