Confusing error messages #95

New Issue

Open

opened 2024-03-13 11:31:46 +01:00 by Jookia · 1 comment

Jookia commented

2024-03-13 11:31:46 +01:00

When fetching a file that doesn't exist a confusing message like this is generated:

<pre>Process 88 stopped
* thread #1: tid = 88, 0x00007f819bf6a1d0, name = 'fhost'
    frame #0:
Process 88 stopped
* thread #8: tid = 88, 0x00007f81a47d7d60 fhost`get(path='/test/') + 27 at fhost.c:139, name = 'fhost/responder', stop reason = invalid address (fault address: 0x30)
    frame #0: {3:#018x} fhost`get(path='/test/') + 27 at fhost.c:139
   136   get(SrvContext *ctx, const char *path)
   137   {
   138       StoredObj *obj = ctx->store->query(shurl_debase(path));
-> 139       switch (obj->type) {
   140           case ObjTypeFile:
   141               ctx->serve_file_id(obj->id);
   142               break;
* Connection #0 to host 0x0.st left intact
(lldb) q</pre>

I received this one when getting a gdb backtrace from a friend who mistakenly typo'd the link and spent a while confused as to where these files were in the crashing program.

When submitting an invalid request like curl -F"file='@myfile.jpg'" it gives a 'Segmentation fault' response.

I hit this trying to figure out how to escape commas and quotes in filenames and almost reported this as a curl bug, but after more debugging found it's just an unhelpful error response.

Could these be changed to something more user friendly and less confusing?

When fetching a file that doesn't exist a confusing message like this is generated: ``` <pre>Process 88 stopped * thread #1: tid = 88, 0x00007f819bf6a1d0, name = 'fhost' frame #0: Process 88 stopped * thread #8: tid = 88, 0x00007f81a47d7d60 fhost`get(path='/test/') + 27 at fhost.c:139, name = 'fhost/responder', stop reason = invalid address (fault address: 0x30) frame #0: {3:#018x} fhost`get(path='/test/') + 27 at fhost.c:139 136 get(SrvContext *ctx, const char *path) 137 { 138 StoredObj *obj = ctx->store->query(shurl_debase(path)); -> 139 switch (obj->type) { 140 case ObjTypeFile: 141 ctx->serve_file_id(obj->id); 142 break; * Connection #0 to host 0x0.st left intact (lldb) q</pre> ``` I received this one when getting a gdb backtrace from a friend who mistakenly typo'd the link and spent a while confused as to where these files were in the crashing program. When submitting an invalid request like curl -F"file='@myfile.jpg'" it gives a 'Segmentation fault' response. I hit this trying to figure out how to escape commas and quotes in filenames and almost reported this as a curl bug, but after more debugging found it's just an unhelpful error response. Could these be changed to something more user friendly and less confusing?

Victoria commented

2024-03-13 19:37:24 +01:00

This seems not to be an actual "Segmentation fault" error. i got this before. it seems to be an inside joke for a 404 page
https://git.0x0.st/mia/0x0/src/branch/master/templates/404.html

This seems not to be an actual "Segmentation fault" error. i got this before. it seems to be an inside joke for a 404 page https://git.0x0.st/mia/0x0/src/branch/master/templates/404.html