Bug 2638 - MonoDevelop crashes when stopping debugging, Fedora 16
Summary: MonoDevelop crashes when stopping debugging, Fedora 16
Status: RESOLVED FIXED
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: Debugger ()
Version: 2.8.1
Hardware: PC Linux
: --- normal
Target Milestone: ---
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2011-12-25 17:09 UTC by Dumitru
Modified: 2012-04-04 17:12 UTC (History)
1 user (show)

Tags:
Is this bug a regression?: ---
Last known good build:


Attachments
Crash log (34.13 KB, text/x-log)
2012-01-31 23:22 UTC, Dumitru
Details
Sample MD solution (27.73 KB, application/x-gzip)
2012-01-31 23:23 UTC, Dumitru
Details
MD with frozen pad (231.19 KB, image/png)
2012-02-01 20:16 UTC, Dumitru
Details


Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.


Please create a new report on Developer Community or GitHub with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:
Status:
RESOLVED FIXED

Description Dumitru 2011-12-25 17:09:12 UTC
MD crashes in debug mode, at the moment of interruption of the debugging session.
It happens very often, after each 2-3 stopping cycles.

System: Fedora 16
Attached is the console output at the moment of crash.
Comment 1 Jeffrey Stedfast 2012-01-06 17:43:27 UTC
looks like you forgot to add the console output.

That said, a lot of fixes have gone into the debugger since 2.8.1, any chance you could test a newer version?

2.8.6 should be out soon.
Comment 2 Dumitru 2012-01-31 23:22:10 UTC
OK, here's more info.

Uninstalled Mono, GTK# and Monodevelop, completely from my Fedora 16 machine.
Installed from sources the above mentioned packages into /usr/local, latest versions as of 31 Janv. (i.e Mono 2.10.8, GTK# 2.12.10 and Monodevelop 2.8.6)

The error persists.

It look like the problem isn't in Mono/Monodevelop, but rather within GTK itself.

I'm attaching the error log, and also the Monodevelop project that leads to said error.
Steps to reproduce:
  1) Open up the GoldenBoomerang solution in MD.
  2) Set a breakpoint (if not there already) in file Loader.cs, line 54, which is:  defx.Load(Path.Combine(path, FILENAME_DEFX));
  3) Click on button Debug (F5)
  4) When execution stops at breakpoint, click again Debug (F5) to continue.
  5) Repeat step 3)
  6) Repeat step 4) <--- here's where MD crashes.


Now I'm not even sure whether it's a Mono bug, Monodevelop bug, GTK/GTK# bug, or Fedora's own problem. I mean, it can't be right that the debugging don't work for any MD project whatsoever.
I hope we figure this out.

Meanwhile I need a way to debug my app, are there any alternative means of debugging (preferably graphically) a Mono app ?

ATTACHMENT DESCRIPTION:
*) monodevelop-stdout.log - error log of MD custom build from sources, as described above. The stock MD has a similar output, particularly the "__gtk_container_propagate_expose" part.
*) GoldenBoomerang.tar.bz2 - archived package of sample MD solution, which causes the crash.


Thanx,
Dimitri.
Comment 3 Dumitru 2012-01-31 23:22:37 UTC
Created attachment 1297 [details]
Crash log
Comment 4 Dumitru 2012-01-31 23:23:29 UTC
Created attachment 1298 [details]
Sample MD solution
Comment 5 Mikayla Hutchinson [MSFT] 2012-02-01 15:06:49 UTC
Could you please try a newer 2.8.6.x release that includes this commit?

https://github.com/mono/monodevelop/commit/411a2dfb6492138e4a8b624307e52961b038b517
Comment 6 Dumitru 2012-02-01 20:16:13 UTC
Wow, amazing, it works !

MD doesn't crash anymore, cool, but it leaves an ugly half-panned pad area like you can see in the image. I can live with that, of course, but would be nice if I could recover that real estate.

Thank you for the fix.
Dimitri.
Comment 7 Dumitru 2012-02-01 20:16:48 UTC
Created attachment 1302 [details]
MD with frozen pad
Comment 8 Mikayla Hutchinson [MSFT] 2012-02-01 20:26:02 UTC
Interesting. Is that reproducible?
Comment 9 Mikayla Hutchinson [MSFT] 2012-04-04 17:12:47 UTC
I disabled pad animation in master because people complained it made MD feel slow. As a side-effect, that problem should now be impossible.