@atmasphere, yes, no
404 anymore. @CAW, so the reason
for crash may be otner than segmentation fault. I will improve the
backtrace uploader in the near future...
Looks like 0.4.2.1 removed the menu option to force a crash,
too. So I can't test that to ensure the uploader is working under
that condition.
What is the binary for the uploader? And where is the backtrace
stored in the filesystem? I'd like to see if it's written anything
out, and if so, I could manually run the uploader from an
xterm.
8 comments so far
0.4.2 did that once, but it just worked a minute ago. I'd say 0.4.x is less stable than vanilla 0.4. Like the gestures tho
4 months, 1 week ago by bogart.
so the 404 is clear?
4 months, 1 week ago by atmasphere.
I've had Mauku (0.4.2.1) crash a few times on its own now, and have not been prompted to upload the backtrace. Any suggestions?
4 months, 1 week ago by CAW.
@atmasphere, yes, no 404 anymore. @CAW, so the reason for crash may be otner than segmentation fault. I will improve the backtrace uploader in the near future...
4 months, 1 week ago by hhedberg.
Looks like 0.4.2.1 removed the menu option to force a crash, too. So I can't test that to ensure the uploader is working under that condition.
What is the binary for the uploader? And where is the backtrace stored in the filesystem? I'd like to see if it's written anything out, and if so, I could manually run the uploader from an xterm.
4 months, 1 week ago by CAW.
The binary is /usr/bin/miaouw-backtrace-uploader. The backtrace is not stored but piped to the binary directly from signal handler.
I could add the menu option in unstable builds.
4 months, 1 week ago by hhedberg.
Ah, if it's not stored, then not much I can do. It has to be dying on something the signal handler isn't currently configured to catch then.
4 months, 1 week ago by CAW.
Propably. I suspect the abort signal that is sent when the glib outputs a fatal error message. Only the segmentation fault is catched currently.
4 months, 1 week ago by hhedberg.