Thomasims / GCrash

Garry's Mod SIGSEGV handler to dump the Lua state

15 stars 5 forks source link

Empty lua stack and the main lua stack contains only gcrash #4

Closed Flapchik closed 2 years ago

Flapchik commented 3 years ago

Hey. Thanks for developing this module. Unfortunately, I have problems. Please help me to solve them.

Seg fault occured.

Main Lua stack:
#0  lua/autorun/server/gcrach.lua:26 in anonymous function() <26-45>

Lua crash handler:

Frame #0, @lua/autorun/server/gcrach.lua:26:
  write = function: 0xdcc17760

and

Seg fault occured.

Main Lua stack:

Lua crash handler:

Thomasims commented 3 years ago

Hi, I'm investigating the reason why the first one shows up (I have another case where GCrash appears in the trace), so far I haven't found a reason to suspect GCrash is causing any issue itself. The second is simply a segfault happening when no Lua is running. GCrash cannot help with these cases, I recommend just sending the coredump ('core' file) to Facepunch for proper analysis.

GranDaddySmoke commented 2 years ago

Seg fault occured.

Main Lua stack:

0 lua/autorun/server/gcrash.lua:27 in anonymous function() <27-46>

Lua crash handler: I have been getting this a lot.

Thomasims commented 2 years ago

I haven't found anything new since my last message, my best guess is that the Lua state gets corrupted to the point where calling a lua function on top of that stack just panics out again. This theory is shaky and probably not correct but there's nothing else I can do, if it's corrupted that bad I can't reliably inspect it.