Package: geany Version: 0.14-1 Severity: grave --- Please enter the report below this line. ---
This bug was introduced after upgrading. Before that, when I compiled "programme.c", the default output was "programme". After the upgrade, the default output is "a.out" but the execution script that you run with build -> execute links to "./programme" Now I hear you asking: "OK, but it is very easy to fix; why did you submit this bug as grave?". Because it may go unnoticed and have fatal consequences: let us suppose that an engineer working on rocket science often runs numerical simulations. He upgraded geany today, he opens a piece of code he wrote last week, *changes some parameters*, selects build -> build and build -> execute. He *did not notice anything, but he actually ran the executable of last week (named "programme") instead of the intended one (named "a.out") with the old parameters!!!!* Now the rocket is built and it simply does not work :-) Something similar to this case (but with less grave consequences :-) ) happened to me today: I noticed that the executable was running with another values for the parameters, and it was driving me bananas :-) --- System information. --- Architecture: i386 Kernel: Linux 2.6.24-1-686 Debian Release: lenny/sid 990 unstable www.debian-multimedia.org 990 unstable ftp.uk.debian.org 500 stable dl.google.com 500 experimental www.debian-multimedia.org 1 experimental ftp.uk.debian.org --- Package information. --- Depends (Version) | Installed =================================-+-================ libatk1.0-0 (>= 1.20.0) | 1.22.0-1 libc6 (>= 2.7-1) | 2.7-10 libcairo2 (>= 1.2.4) | 1.6.4-1+b1 libgcc1 (>= 1:4.1.1-21) | 1:4.3.0-3 libglib2.0-0 (>= 2.16.0) | 2.16.3-2 libgtk2.0-0 (>= 2.12.0) | 2.12.9-3 libpango1.0-0 (>= 1.20.2) | 1.20.2-2 libstdc++6 (>= 4.1.1-21) | 4.3.0-3
