I have encountered this on my machine, along with a friends. When trying to run bblaunch with no commands (or even with command line arguments), the program segfaults. I narrowed it down to line 173 of bblaunch.c: sprintf(launchargs.call, "%s", (char *)atoi(argv[0])); Casting an integer to a character string is causing the program to access invalid memory resulting in a segmentation fault. After going through the code, I cannot find the significance of this cast or the atoi conversion, or even the significance of the entire line for that matter. After applying the patch I wrote, the program seems to run flawlessly. Reproducible: Always Steps to Reproduce: 1. Run bblaunch 2. 3. Actual Results: Segmentation Fault Expected Results: The software should run.
Created attachment 33323 [details] bblaunch-0.0.3-r1.ebuild An updated ebuild bumped to -r1
Created attachment 33325 [details, diff] files/0.0.3.patch Patch to fix segmentation fault.
for some reason the ebuild refuses to run out of the overlay directory...
gah, ignore me, i'm an idiot. is there some way to have the ebuild download the patch automagically, tho?
Put the patch URI in SRC_URI, copy it into ${FILESDIR} from ${DISTDIR}/<patch name> -- patch as normal.
thanks for the patch. fixed in cvs - no revision bump. please reemerge.