GregoryCannon / GregoryCannon/StackRabbit
Loading stackrabbit.lua irrecoverably crashes Fceux: *** buffer overflow detected ***: terminated
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 462
- Forks
- 50
- PR merge metrics
- No merged PRs in 30d
Description
When loading stackrabbit.lua, Fceux freezes for a split-second, then the window closes without an error message. When running from the terminal, this is the full output:
~/StackRabbit/src/fceux$ fceux
Starting FCEUX 2.6.5...
NTSC mode set
NTSC mode set
Running on Platform: xcb
Emulator Start
GL Version: 4.6 (Compatibility Profile) Mesa 26.0.1-2
Activate Recent ROM: /home/ne04/Tetris.nes
Loading /home/ne04/Tetris.nes...
PRG ROM: 2 x 16KiB = 32 KiB
CHR ROM: 2 x 8KiB = 16 KiB
ROM CRC32: 0x1394f57e
ROM MD5: 0x5b0e571558c8c796937b96af469561c6
Mapper #: 1
Mapper name: MMC1
Mirroring: Vertical
Battery-backed: No
Trained: No
Power on
No Debug Windows Open: Skipping loading of breakpoint data
Initializing video... Video Mode: 256 x 224 x 32 bpp
Loading SDL sound with pulseaudio driver...
NTSC mode set
NTSC mode set
*** buffer overflow detected ***: terminated
Aborted (core dumped) fceux
@BenP1236691 you instructed people to ping you in new issues that aren't listed in the FAQ.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the failure by loading stackrabbit.lua in FCEUX 2.6.5 from a terminal and capture the reported buffer-overflow output. Investigate the loading path using the script and FCEUX entry points named in the report; done means the script loads without freezing, terminating, or producing the buffer-overflow failure.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- lua
- Domain
- game-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100