Re: Equivalent of the gtk g_object_ref/unref functions in gtkmm?
- From: Murray Cumming <murrayc murrayc com>
- To: Jef Driesen <jefdriesen hotmail com>
- Cc: gtkmm-list gnome org
- Subject: Re: Equivalent of the gtk g_object_ref/unref functions in gtkmm?
- Date: Mon, 26 Mar 2007 21:02:44 +0200
On Mon, 2007-03-26 at 21:00 +0200, Jef Driesen wrote:
> Murray Cumming wrote:
> > On Mon, 2007-03-26 at 16:30 +0200, Jef Driesen wrote:
> >> Jonathon Jongsma wrote:
> >>> On 3/26/07, Jef Driesen <jefdriesen hotmail com> wrote:
> >>>> The application works fine, but closing the main window results in a
> >>>> segmentation fault (core dump). As far as I can tell (from a gdb
> >>>> backtrace) the crash is not in my own code, but somewhere inside the
> >>>> gtk(mm) library.
> >>> Could you provide the backtrace? that might be helpful information.
> >> Sometimes I don't get the segmentation fault, but only a large number of
> >> errors. See attachment for both the backtrace and the errors.
> >
> > If you get glib errors, try debuggin with --g-fatal-warnings, or with a
> > breakpoing on g_log. Then you'll get a backtrace at the relevant point.
>
> Backtrace attached, although it doesn't seem to provide much more
> information to me.
>
> > valgrind's memcheck is also incredibly helpful. Trust us on this. You
> > won't regret trying it.
>
> I get lots of errors from valgrind, but I also get them for the trivial
> program
If you show us, we might be able to make sense of things.
By the way, what Linux distribution is this? Are you using just the
standard compiler or have you done anything unusual?
> int main (int argc, char *argv[])
> {
> Gtk::Main kit(argc, argv);
> Gtk::Window window;
> kit.run(window);
> return 0;
> }
>
> But to be honest I never used valgrind before, so I could be using it wrong.
--
Murray Cumming
murrayc murrayc com
www.murrayc.com
www.openismus.com
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]