After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 660618 - Run program stops working after a while
Run program stops working after a while
Status: RESOLVED DUPLICATE of bug 662288
Product: anjuta
Classification: Applications
Component: plugins: run-program
git master
Other Linux
: Normal normal
: ---
Assigned To: Sébastien Granjoux
Anjuta maintainers
Depends on:
Blocks:
 
 
Reported: 2011-10-01 09:34 UTC by Sébastien Granjoux
Modified: 2011-10-23 21:30 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Add more debugging information (9.33 KB, patch)
2011-10-01 09:50 UTC, Sébastien Granjoux 		none Details | Review

Description Sébastien Granjoux 2011-10-01 09:34:47 UTC 
Maybe I'm doing something wrong... I first experienced the problem with 
the 3.0.x version of Anjuta, and installed 3.2 to test it there.

After a while, editing/compiling/running, for some reason the 'Run
program' doesn't work anymore. The 'Run' menu shows the program isn't
running anymore. Compilation works, but clicking on 'Run' doesn't do
anything at all.

Running a debug session still functions normally though, and at no time
stopped.

The only way to re-enable 'Run' is to restart Anjuta.
Comment 1 Sébastien Granjoux 2011-10-01 09:50:53 UTC 
Created attachment 197952 [details] [review]
Add more debugging information

Here is a patch adding more debugging information. Could you apply it (patch -p1 < add_gwarning.patch), recompile Anjuta and check what's happen when you get the bug again?

I have added additional warning messages. So you need to run anjuta in a terminal, save the warning messages and post them on this bug. I'm interested mainly by the one starting with "run plugin:".


I think I have found one place that could explain the behavior you have observed. But I don't know how it can go here, perhaps by aborting a build or trying to build the executable several times

You could be able to make it works again without restarting Anjuta if you select a new executable in the parameter dialog, run it and then switch back to the original executable.
Comment 2 Sébastien Granjoux 2011-10-23 21:30:55 UTC 

*** This bug has been marked as a duplicate of bug 662288 ***