Re: GLib-GObject-CRITICAL **: g_value_get_boolean: assertion `G_VALUE_HOLDS_BOOLEAN (value)' failed

[Glus Xof <gtglus gmail com>]

I make this,

===
(gdb) break g_return_if_fail_warning()
Function "g_return_if_fail_warning()" not defined.
Make breakpoint pending on future shared library load? (y or [n]) y

Breakpoint 1 (g_return_if_fail_warning()) pending.
(gdb) run
===

Execution did not stop...

Glus

2011/3/26 Kjell Ahlstedt <kjell ahlstedt bredband net>:
> I'm afraid I don't know anything about Nemiver. The only debugger I've
> used on Linux is gdb (a command line debugger). From your last email I
> get the impression that Nemiver is a GUI application where you mark
> breakpoints in the source code. Then perhaps it's difficult or even
> impossible to set a breakpoint in the GLib function
> g_return_if_fail_warning, if you don't have the source code of GLib.
>
> With gdb it's usually possible to set a breakpoint with 'break' or
> 'rbreak' even if you don't have the source code.
>
> Kjell
>
> lör 2011-03-26 klockan 11:25 +0100 skrev Glus Xof:
>> Just half an hour, I reconnected and I'm trying to reproduce what Mr
>> Yann recommends.
>>
>> I don't have experience in debugging but I'm motivate to learn...
>>
>> Just I download and installed Nemiver, and now trying to understand
>> the environment.
>>
>> With F8, I'm been able to mark a breakpoint... but I need more help to
>> see beyond...
>>
>> I just see that there is an option to call a function... but how to
>> mark a breakpoint to g_return_if_fail_warning ...?
>>
>> Glus
>>
>> 2011/3/26 Kjell Ahlstedt <kjell ahlstedt bredband net>:
>> > Hi Glus,
>> > The message is printed by a function called g_return_if_fail_warning. If
>> > your debugger can set a breakpoint at the entry to that function, and
>> > then print a backtrace, I think that would be a good start of your
>> > debugging session.
>> >
>> > Kjell
>> >
>> > lör 2011-03-26 klockan 09:06 +0100 skrev Yann LEYDIER:
>> >> On 26/03/11 08:45, Glus Xof wrote:
>> >> > What do you think about it ?
>> >>
>> >> I think that it comes from a widget contained in you dialog.
>> >> Try debugging your application (breakpoint on the dialog.run(), then
>> >> step by step) to locate the function that throws the "exception").
>> >>
>> >> If you don't have a debugger, you can use Visual Studio Express on
>> >> Windows or Nemiver on Linux (and don't forget to compile your app with
>> >> "g++ -g").
>> >>
>> >> And please be patient when you don't get an answer, we are all volunteers.
>> >>
>> >> yann
>> >>
>> >> > 2011/3/25 Glus Xof<gtglus gmail com>:
>> >> >> Hi,
>> >> >>
>> >> >> My app, suddenly, at execution time, throws me messages like this,
>> >> >>
>> >> >> (***** : ****) GLib-GObject-CRITICAL **: g_value_get_boolean:
>> >> >> assertion `G_VALUE_HOLDS_BOOLEAN (value)' failed
>> >> >>
>> >> >> It seems that from a code line who says,
>> >> >>
>> >> >> gint d_result = m_dialog.run();
>> >> >>
>> >> >> Obviously,
>> >> >>
>> >> >> Gtk::Dialog m_dialog...
>> >> >>
>> >> >> What's wrong ???
>> >> >>
>> >> >> Glus
>> >> >>
>> >> > _______________________________________________
>> >> > gtkmm-list mailing list
>> >> > gtkmm-list gnome org
>> >> > http://mail.gnome.org/mailman/listinfo/gtkmm-list
>> >>
>> >> _______________________________________________
>> >> gtkmm-list mailing list
>> >> gtkmm-list gnome org
>> >> http://mail.gnome.org/mailman/listinfo/gtkmm-list
>> >
>> >
>> > _______________________________________________
>> > gtkmm-list mailing list
>> > gtkmm-list gnome org
>> > http://mail.gnome.org/mailman/listinfo/gtkmm-list
>> >
>
>
>