Description of problem: “unifdef -m” results in a segmentation fault. Version-Release number of selected component (if applicable): unifdef-2.10-6.fc26.x86_64 How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: unifdef crashes with SIGSEGV. Expected results: Some sort of error message, or no output at all (and exit status 0). Additional info: (gdb) r Starting program: /usr/bin/unifdef -m Program received signal SIGSEGV, Segmentation fault. processinout (ifn=<optimized out>, ofn=0x0) at unifdef.c:392 392 if (strcmp(ofn, "-") == 0) { (gdb) bt #0 processinout (ifn=<optimized out>, ofn=0x0) at unifdef.c:392 #1 0x00000000004016d1 in main (argc=<optimized out>, argv=0x7fffffffdde8) at unifdef.c:362 (gdb) info locals __s2 = 0x0 __result = <error reading variable __result (Cannot access memory at address 0x0)> __s2_len = 1 st = {st_dev = 0, st_ino = 0, st_nlink = 0, st_mode = 0, st_uid = 0, st_gid = 0, __pad0 = 0, st_rdev = 0, st_size = 140737354132568, st_blksize = 2983696132577082368, st_blocks = 140737488346160, st_atim = { tv_sec = 6320504, tv_nsec = 4200304}, st_mtim = {tv_sec = 2, tv_nsec = 4210376}, st_ctim = {tv_sec = 0, tv_nsec = 0}, __glibc_reserved = {0, 4200992, 4200992}} (gdb) l 387 linefile = ifn; 388 input = fopen(ifn, "rb"); 389 if (input == NULL) 390 err(2, "can't open %s", ifn); 391 } 392 if (strcmp(ofn, "-") == 0) { 393 output = fbinmode(stdout); 394 process(); 395 return; 396 } (gdb)
This message is a reminder that Fedora 26 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 26. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '26'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 26 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Still present in unifdef-2.10-9.fc28.x86_64.
This bug appears to have been reported against 'rawhide' during the Fedora 29 development cycle. Changing version to '29'.
This message is a reminder that Fedora 29 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 29 on 2019-11-26. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '29'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 29 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 29 changed to end-of-life (EOL) status on 2019-11-26. Fedora 29 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.
can still reproduce this on F30
also a problem on F31
This message is a reminder that Fedora 31 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 31 on 2020-11-24. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '31'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 31 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 31 changed to end-of-life (EOL) status on 2020-11-24. Fedora 31 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.