Repository navigation
Debugging a crash #55
Description
Started using this library:
but it crashes in non-debug mode, and in debug mode no errors. catching exception does not help.
how to get logs out of the problem?
In that example, crash can be avoided by not using any plex server related in section_types method
this still crashes even faulti part is catch'ed:
@cached_property
def section_types(self):
try:
self.server
except Exception as e:
...
return {}tl;dr: crashes on macos in normal mode. does not crash under -f, does not crash under -d, and under -d no known exception is thrown.
Activity
[-]Debugging an crash[/-][+]Debugging a crash[/+]SimonHeimberg commentedon Jul 24, 2024
You already tried
-f, which often helped me. 🤔Suggesting some ideas:
stdout to file
Then see if any error gets written into ~/.fuse_debug.txt
redirect traceback
Or a similar idea, write your own function replacing
sys.get_traceback()to do custom printing, see https://docs.python.org/3/library/sys.html#sys.excepthook or http://stackoverflow.com/questions/6234405/ddg#16993115debugger
Possibly the debugger can help. But I fail to get anything more useful than implementing one of the above things without changing the code. Anyway, redirect stdout:
python3 -m pdb ./xxx/theCodeToDebug.pyThe debugger is left when main() is called, and I know no possibility to avoid this.