Red Hat Bugzilla – Bug 209346
Frysk crashes when I choose to "Debug an existing process"
Last modified: 2007-11-30 17:11:45 EST
Description of problem: I launch in execution Frysk Startup Manager. I select to
"Debug an Existing Process", and I select casually various processes. Simply no
information is displayed, and program returns to main window; or, the debugger
shows me "No information available for this stack frame", then crashes.
Version-Release number of selected component (if applicable):
Version which ships with default installation of Fedora Core 6 Test 3
Steps to Reproduce:
1. Launch Frysk Startup Manager
2. Choose "Debug an existing process"
3. Choose various processes, casually, till the debugger is displayed
Additional info: I run Frysk from command line (/usr/bin/frysk), and when Frysk
crashed, I was able and have backtrace (see attached text file "fryskCrash".
Created attachment 137762 [details]
Backtrace of a Frysk crash
This sounds like the upstream bug here:
and is tracked in upstream here:
While we investigate these issues in Java-GNOME, you can workaround it with:
Can you confirm similar results?
Yes, I can confirm with
I'm able and run without crashes.
When I choose to "Debug an existing process", I always have "No information
available for this stack frame", and a "Blocking" message in terminal.
In one case I had a Java NullPointerException error; sorry I wasn't able and
take note of the specific process.
Created attachment 139544 [details]
Free sub regions created in Drawable using gdk_region_destroy
Drawable.c, when creating regions, was setting the "free" method to g_free
instead of gdk_region_destroy.