-
Notifications
You must be signed in to change notification settings - Fork 10
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
jackpatch crashing at load (buffer overflow) #100
Comments
This fixes the issue for me:
|
if pipewire crashes and real jack does not, we should fix pipewire side instead of trying to mitigate the issues. where does the overflow happen? |
jackpatch crashes, it's obviously the clients fault, the line number is in the GDB log.
|
ok that part makes sense. but there is no need to change the stack array into alloca, that is an unrelated change. |
The changes are related, they both concern 'REAL_JACK_PORT_NAME_SIZE'. If a fixed buffer size of 512 bytes is ok (which I don't think it is), then there is no need for 'REAL_JACK_PORT_NAME_SIZE' in the first place and you can just use 'snprintf(buf, sizeof(buf), ...)'. If 'alloca' is not portable, just use an 'malloc'. |
This happens when jackpatch is run under pipewire-jack.
REAL_JACK_PORT_NAME_SIZE
may not have been initialized, yet?Version
Invocation
GDB dump
Config (JACKPatch.nBKXL.jackpatch)
The text was updated successfully, but these errors were encountered: