x11-plugins/wmfrog 0.2.0 compiles and runs on amd64 without any apparent problems. Suggest you consider removing the ~ from amd64. Reproducible: Always
Small problem: I just tried testing this (recently up-to-date ~amd64 system), and got the following error when I tried running: $ wmfrog -s KLWM *** buffer overflow detected ***: wmfrog terminated ======= Backtrace: ========= /lib/libc.so.6(__fortify_fail+0x37)[0x7fa5dde667e7] /lib/libc.so.6[0x7fa5dde645c0] /lib/libc.so.6[0x7fa5dde638b9] /lib/libc.so.6(_IO_default_xsputn+0x85)[0x7fa5dddf0935] /lib/libc.so.6(_IO_vfprintf+0x35b4)[0x7fa5dddc41f4] /lib/libc.so.6(__vsprintf_chk+0x9d)[0x7fa5dde6395d] /lib/libc.so.6(__sprintf_chk+0x80)[0x7fa5dde638a0] wmfrog[0x4029ec] /lib/libc.so.6(__libc_start_main+0xe6)[0x7fa5ddd9ca26] wmfrog[0x4014b9] ======= Memory map: ======== 00400000-00425000 r-xp 00000000 08:05 6632499 /usr/bin/wmfrog 00624000-00625000 r--p 00024000 08:05 6632499 /usr/bin/wmfrog 00625000-0062d000 rw-p 00025000 08:05 6632499 /usr/bin/wmfrog 02047000-020c5000 rw-p 02047000 00:00 0 [heap] 7fa5dcd24000-7fa5dcd39000 r-xp 00000000 08:05 7328655 /lib64/libgcc_s.so.1 7fa5dcd39000-7fa5dcf38000 ---p 00015000 08:05 7328655 /lib64/libgcc_s.so.1 7fa5dcf38000-7fa5dcf39000 r--p 00014000 08:05 7328655 /lib64/libgcc_s.so.1 7fa5dcf39000-7fa5dcf3a000 rw-p 00015000 08:05 7328655 /lib64/libgcc_s.so.1 7fa5dcf3a000-7fa5dcf3f000 r-xp 00000000 08:05 435290 /usr/lib64/libXfixes.so.3.1.0 7fa5dcf3f000-7fa5dd13e000 ---p 00005000 08:05 435290 /usr/lib64/libXfixes.so.3.1.0 7fa5dd13e000-7fa5dd13f000 r--p 00004000 08:05 435290 /usr/lib64/libXfixes.so.3.1.0 7fa5dd13f000-7fa5dd140000 rw-p 00005000 08:05 435290 /usr/lib64/libXfixes.so.3.1.0 7fa5dd140000-7fa5dd149000 r-xp 00000000 08:05 435300 /usr/lib64/libXrender.so.1.3.0 7fa5dd149000-7fa5dd348000 ---p 00009000 08:05 435300 /usr/lib64/libXrender.so.1.3.0 7fa5dd348000-7fa5dd349000 r--p 00008000 08:05 435300 /usr/lib64/libXrender.so.1.3.0 7fa5dd349000-7fa5dd34a000 rw-p 00009000 08:05 435300 /usr/lib64/libXrender.so.1.3.0 7fa5dd34a000-7fa5dd353000 r-xp 00000000 08:05 442303 /usr/lib64/libXcursor.so.1.0.2 7fa5dd353000-7fa5dd552000 ---p 00009000 08:05 442303 /usr/lib64/libXcursor.so.1.0.2 7fa5dd552000-7fa5dd553000 r--p 00008000 08:05 442303 /usr/lib64/libXcursor.so.1.0.2 7fa5dd553000-7fa5dd554000 rw-p 00009000 08:05 442303 /usr/lib64/libXcursor.so.1.0.2 7fa5dd554000-7fa5dd556000 r-xp 00000000 08:05 3421324 /usr/lib64/libXau.so.6.0.0 7fa5dd556000-7fa5dd755000 ---p 00002000 08:05 3421324 /usr/lib64/libXau.so.6.0.0 7fa5dd755000-7fa5dd756000 r--p 00001000 08:05 3421324 /usr/lib64/libXau.so.6.0.0 7fa5dd756000-7fa5dd757000 rw-p 00002000 08:05 3421324 /usr/lib64/libXau.so.6.0.0 7fa5dd757000-7fa5dd75c000 r-xp 00000000 08:05 30870 /usr/lib64/libXdmcp.so.6.0.0 7fa5dd75c000-7fa5dd95b000 ---p 00005000 08:05 30870 /usr/lib64/libXdmcp.so.6.0.0 7fa5dd95b000-7fa5dd95c000 r--p 00004000 08:05 30870 /usr/lib64/libXdmcp.so.6.0.0 7fa5dd95c000-7fa5dd95d000 rw-p 00005000 08:05 30870 /usr/lib64/libXdmcp.so.6.0.0 7fa5dd95d000-7fa5dd95f000 r-xp 00000000 08:05 7815380 /lib64/libdl-2.10.1.so 7fa5dd95f000-7fa5ddb5f000 ---p 00002000 08:05 7815380 /lib64/libdl-2.10.1.so 7fa5ddb5f000-7fa5ddb60000 r--p 00002000 08:05 7815380 /lib64/libdl-2.10.1.so 7fa5ddb60000-7fa5ddb61000 rw-p 00003000 08:05 7815380 /lib64/libdl-2.10.1.so 7fa5ddb61000-7fa5ddb7c000 r-xp 00000000 08:05 6440749 /usr/lib64/libxcb.so.1.1.0 7fa5ddb7c000-7fa5ddd7c000 ---p 0001b000 08:05 6440749 /usr/lib64/libxcb.so.1.1.0 7fa5ddd7c000-7fa5ddd7d000 r--p 0001b000 08:05 6440749 /usr/lib64/libxcb.so.1.1.0 7fa5ddd7d000-7fa5ddd7e000 rw-p 0001c000 08:05 6440749 Aborted Are you sure this is ready to go stable?
amd64 stable, closing
The buffer overflow issue always happened. I checked the code, and found the process terminated at "sprintf(FileName, "%s/%s", folder, StationID);"(wmFrog.c: 216) Because the FileName buffer size is 10 bytes(wmFrog.c: 69) not MAX_PATH. Please reopen the bug.
Revision -r1 fixes the issue. Stabilized for x86. AMD64, please test and mark stable.
Works fine Stable on amd64 All arches done
