Error message must be more meaningful. Not just Got Tribler core error: 1.

[KOLANICH]

Please, fill all relevant items:

• I have read CONTRIBUTING.rst

• I have tried with the latest pre-release version and I still can reproduce the issue.

Tribler version/branch+revision:

From git.

Operating system and version:

Doesn't matter. I use Linux-based OS with overcommit disabled.

Steps to reproduce the behavior:

When tribbler core crashes, it is hard to figure out what exactly happened.

Expected behavior:

The GUI should have access to all the error messages of core.

Actual behavior:

The message is only Got Tribler core error: 1.

Relevant log file output:

All the logs are empty.

[devos50]

First, our contributing guide can be found here.

The GUI should have access to all the error messages of core.

I see the issue here and get the frustration. Tribler consists of two processes: the GUI and the core. The core process is spawned by the GUI process. It is very likely that the message you receive is an error that immediately happens when the GUI process spawns the core process. We redirect all logging of the core process through the GUI and monitor if there are any tracebacks. These tracebacks, however, might never be visible, making this issue very hard to debug. There can be many causes for this behaviour, e.g., the Python interpreter has crashed or some library is causing havoc.

Which version/branch of Tribler are you running?

[KOLANICH]

Tribler consists of two processes: the GUI and the core.

Yeah, I know. I have looked into the sources. Had to workaround by adding the code dumping the authentication info for core and then starting the core manually to see what happens.

Which version/branch of Tribler are you running?

The default branch in the repo.

[drew2a]

This issue has been addressed in

• Improve Core Process Error Handling: Restart on Crash and Prompt for Error Reporting #7647