-
For sending, if `ZMessage` is created in stack frame, segmentation fault was reported.
Following code is example.
```zig
fn someFunction(allocator: Allocator, socket: *ZSocket, text: []const u8…
-
The following assert occurs in the `ToArrowTest.NestedList` test in `INTEROP_TEST`:
```
$ gtests/INTEROP_TEST --gtest_filter=ToArrowTest.NestedList
Note: Google Test filter = ToArrowTest.NestedList
[…
-
Executing test_server results in a segmentation fault created in the execution of the BuildAndStart() method. Below is the stack backtrace produced by GDB.
```
(gdb) bt
#0 0x00007ffff7da4d74 in…
-
### Zig Version
0.12.0-dev.1245+a07f288eb
### Steps to Reproduce and Observed Behavior
1. Create a file `bug.zig` with the following content:
```zig
const std = @import("std");
pub fn main() !…
-
When running this basic code I get a segmentation fault on the line where I `xawait`.
This is the code:
```const std = @import("std");
const libcoro = @import("libcoro");
fn myCoroutine(x: *us…
-
When using GPU computation, the ID list in trackparticle seems to be reassigned based on the current position at each timestamp, while with CPU computation, particle IDs are inherited across different…
-
Below is the program code for test.cpp.
```
#include
#include
using namespace cl::sycl;
int main() {
queue q;
const int size = 1024;
std::vector data(size, 1);
buff…
-
These warnings likely indicate real errors:
```
./CCvcExceptions.hh:49:101: warning: address of stack memory associated with local variable 'myMessage' returned [-Wreturn-stack-address]
con…
-
Custom allocators (`#[global_alloc]`) come with all sorts of exciting interactions with the operational semantics:
- The compiler is allowed to optimize away calls to them even if these calls have sid…
-
checked by ndk-stack
********** Crash dump: **********
signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x49c
SIGSEGV(SEGV_MAPERR) Address Not Mapped To Object
Stack frame #00 pc 0007ad16 …