Crashpad + demo issues
Closed this issue · 5 comments
I've been trying to evaluate crashpad (along with the backtrace service), and sadly even running the demo doesn't seem to work properly for me.
I've tried on arm-based macOS and on x64 Ubuntu.
What macOS gives out is:
$ ./demo_macos
Crashpad URL: https://submit.backtrace.io/yolo/c5a3a1675dbcfa1d12fd7efbc7bef9350874654e55ff86478115c8bc073f54dc/minidump
Crashpad handler: ~/Developer/github/backtrace-labs/crashpad/cbuild/handler/handler
Crashpad database: mydb
45
50
1
[57888:8921244:20230623,162221.882787:WARNING in_range_cast.h:38] value -634136515 out of range
[57888:8921246:20230623,162221.890429:ERROR directory_reader_posix.cc:42] opendir mydb/attachments/07afdd26-7591-40b0-9f84-86419e11a0a3: No such file or directory (2)
[57888:8921244:20230623,162221.891080:WARNING crash_report_exception_handler.cc:257] UniversalExceptionRaise: (os/kern) failure (5)
[1] 57885 segmentation fault ./demo_macos
It seems that there is an issue with finding the minidump file to upload it to the server (the ERROR above).
On Ubuntu:
Crashpad URL: https://submit.backtrace.io/yolo/c5a3a1675dbcfa1d12fd7efbc7bef9350874654e55ff86478115c8bc00000000/minidump
Crashpad handler: /home/myusername/demo_crashpad_cmake/build/crashpad/handler/handler
Crashpad database: .
45
50
[192834:192834:20230623,163531.683169:FATAL spawn_subprocess.cc:227] posix_spawn: No such file or directory (2)
[192833:192833:20230623,163532.829951:WARNING spawn_subprocess.cc:251] intermediate process terminated by signal 5 (Trace/breakpoint trap) (core dumped)
[192833:192833:20230623,163532.830607:ERROR socket.cc:93] sendmsg: Broken pipe (32)
0
Segmentation fault (core dumped)
Any hints would be appreciated. Thank you.
Hi, it looks like your submission link is not correct - please use the one provided in Project setttings / Integration guides:
Note:
yolo
is the universe name. Yours should be different.
Hi and thanks for replying.
I was actually trying out the example and my assumption was that this ERROR prevents the minidump from being sent out way before hitting the endpoint for the request.
In any case I just created a test project on the backtrace service, so here's the new output on macOS:
$ ./examples/macos/demo/demo_macos
Crashpad URL: https://submit.backtrace.io/holoplot/4d9b92a7ab40dd0ee97f08c4c74b938c193ac9f8b2a7685938ef1cbc2e6daf5e/minidump
Crashpad handler: handler/handler
Crashpad database: .
46
51
1
[64463:8963640:20230623,165844.055195:WARNING in_range_cast.h:38] value -634136515 out of range
[64463:8963641:20230623,165844.062129:ERROR directory_reader_posix.cc:42] opendir attachments/6659f6c4-7081-4c60-95d8-146302a4e4e7: No such file or directory (2)
[64463:8963640:20230623,165844.062766:WARNING crash_report_exception_handler.cc:257] UniversalExceptionRaise: (os/kern) failure (5)
[1] 64459 segmentation fault ./examples/macos/demo/demo_macos
Small update: the uploading seems to work, despite the ERROR... in any case, it must be a crashpad issue because I also tried with the original codebase.
Yes, the log line comes from crashpad itself.
I'm assuming your issue is solved. Feel free to reach out to us if you have further problems.