-
Notifications
You must be signed in to change notification settings - Fork 13
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
segfault in emiting op #42
Comments
I see this even if I set the buffer to larger and larger sizes, up to a size large enough that |
Hi, thanks for the report. Can you reproduce this? Can you share how?
Right.
Right. |
The issue that I linked to this: dart-lang/sdk#48413 has the setup where we found it. It's a pretty deeply nested conglomeration of processes to setup the issue. I haven't been able to reproduce it outside of that context. |
Can you generate a coredump? Also, the buffer is stack-allocated, can you replace that by a malloc() and increase the |
Also can you try the current master? That one gets rid of |
@fangism - I don't know how to update and rebuild |
Looks like we're getting different results, now:
|
I found this error in 41b02a0 (2020-10-10), which is currently packaged in Nixpkgs, but it seems to work in the latest commit c031f8da (2022-03-30). |
Hello, I'm seeing a segfault in the traced app, when it's trying to write to the shared memory buffer back to
fsatrace
:I don't have much more info at this time, but from looking at the source, is this likely to be running past the end of the buffer?
From my reading of main(), all accesses are buffered in the shared memory buffer until the process is complete, and then written, correct? (no concurrent access)
https://github.com/jacereda/fsatrace/blob/master/src/fsatrace.c#L193-L203
And the default logsize is 1MB of text?
https://github.com/jacereda/fsatrace/blob/master/src/fsatrace.h#L4
Which can be overridden by setting the env var
FSAT_BUF_SIZE
?The text was updated successfully, but these errors were encountered: