Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Libretro core: ** stack smashing detected ** error on Linux Ubuntu/Lubuntu/Mint #187

Open
deusX1 opened this issue Jan 4, 2025 · 4 comments
Labels

Comments

@deusX1
Copy link

deusX1 commented Jan 4, 2025

Hello,
Gearboy core (latest release 3.6.1) crashes on my Linux PC (Ubuntu/Mint) with a stack smashing error, but works flawlessly on Windows (same PC) and MacOS.

To be precise, the core is initialized correctly without errors in retro_init(), as well as any GB rom loads correctly in retro_load_game(). The problem arises after the invocation of retro_run().

I'm running the core in a new frontend I recently developed, it works great on a m1 macmini as well as on windows PC.
All the other cores I tested works well under Linux, I encountered this issue only for Gearboy.

Hopes it can help, or to fix the issue on my side if that's the case.

@drhelius
Copy link
Owner

drhelius commented Jan 4, 2025

Thanks for reporting.

I'm assuming the error is in the libretro core only? Could you try the standalone?

If you can compile from sources you can try make DEBUG=1.

This will output more traces. If you can share the traces since the startup of the core it would be great.

@drhelius drhelius added the bug label Jan 4, 2025
@deusX1
Copy link
Author

deusX1 commented Jan 4, 2025

Ok, I will test the standalone version first and will provide the result. thanks.

@drhelius
Copy link
Owner

drhelius commented Jan 4, 2025

Just tested in my Ubuntu box both standalone and libretro with RetroArch and it works.

If you can't run it in a debugger you can try adding "printfs" between function calls in retro_run to see how far it goes.

Does it always happen or just with a specific rom?

@deusX1
Copy link
Author

deusX1 commented Jan 4, 2025

Just tested in my Ubuntu box both standalone and libretro with RetroArch and it works.

If you can't run it in a debugger you can try adding "printfs" between function calls in retro_run to see how far it goes.

Does it always happen or just with a specific rom?

It always happen with any rom.

For the test, yes I can confirm it works as standalone.
I will try the core in retroarch and to put some prints as you suggested.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants