Gtkmm-forge digest, Vol 1 #848 - 3 msgs

[gtkmm-forge-request lists sourceforge net]

Send Gtkmm-forge mailing list submissions to
	gtkmm-forge lists sourceforge net

To subscribe or unsubscribe via the World Wide Web, visit
	https://lists.sourceforge.net/lists/listinfo/gtkmm-forge
or, via email, send a message with subject or body 'help' to
	gtkmm-forge-request lists sourceforge net

You can reach the person managing the list at
	gtkmm-forge-admin lists sourceforge net

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Gtkmm-forge digest..."


gtkmm-forge is the mailing list that receives gtkmm bug reports from bugzilla.  A daily digest is sent to gtkmm-main, to encourage people to help fixing the bugs. Do not try to unsubscribe gtkmm-forge from gtkmm-list.


Today's Topics:

   1. [Bug 163765] New: Glib::Dispatcher crash (bugzilla-daemon bugzilla gnome org)
   2. [Bug 163765] Glib::Dispatcher crash (bugzilla-daemon bugzilla gnome org)
   3. [Bug 140515] Container child properties not wrapped (bugzilla-daemon bugzilla gnome org)

--__--__--

Message: 1
From: bugzilla-daemon bugzilla gnome org
To: gtkmm-forge lists sourceforge net
Cc: 
Date: Wed, 12 Jan 2005 01:07:22 -0500 (EST)
Subject: [gtkmm bugzilla] [Bug 163765] New: Glib::Dispatcher crash

Please DO NOT reply to this by email. All additional comments should be made in
the comments box of this bug report.

 http://bugzilla.gnome.org/show_bug.cgi?id=163765
 glibmm | threads | Ver: 2.4.x

           Summary: Glib::Dispatcher crash
           Product: glibmm
           Version: 2.4.x
          Platform: Other
        OS/Version: All
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: threads
        AssignedTo: gtkmm-forge lists sourceforge net
        ReportedBy: darco voria com
                CC: all-bugs bugzilla gnome org


If Glib::Dispatcher::emit() is called and then that Glib::Dispatcher object is deleted before the signal is 
"dispatched" by the main loop, a crash occurs--even if the sigc::connection for that signal has been 
disconnected.

In my code, emit() is being called from a thread. The Glib::Dispatcher is being deleted from the main 
process.

Not that it would make any difference, but this bug appears both under Linux and Win32.

Here is a backtrace:

#0  0x0828981b in std::list<sigc::slot_base, std::allocator<sigc::slot_base> >::empty() const 
(this=0x892a470) at stl_list.h:628
#1  0x08288981 in sigc::internal::signal_emit0<void, sigc::nil>::emit(sigc::internal::signal_impl*) 
(impl=0x892a468) at signal.h:510
#2  0x40aeb262 in Glib::DispatchNotifier::pipe_io_handler(Glib::IOCondition) (this=0x8caf6a0) at 
signal.h:1584
#3  0x40aeb978 in sigc::internal::slot_call1<sigc::bound_mem_functor1<bool, Glib::DispatchNotifier, 
Glib::IOCondition>, bool, Glib::IOCondition>::call_it(sigc::internal::slot_rep*, Glib::IOCondition const&) 
(rep=0x40aeb160, a_1= 0x10) at mem_fun.h:1838
#4  0x40aefc56 in Glib::IOSource::dispatch(sigc::slot_base*) (this=0x8caf6e8, slot=0xbffff1c0) at slot.h:
512
#5  0x40aef007 in Glib::Source::dispatch_vfunc(_GSource*, int (*)(void*), void*) (callback=0x40aed6b0 
<(anonymous namespace)::glibmm_dummy_source_callback(void*)>, user_data=0x892a470) at 
main.cc:102
#6  0x40bf6d8f in g_main_depth () from /usr/lib/libglib-2.0.so.0
#7  0x40bf7e08 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#8  0x40bf8133 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#9  0x40bf8743 in g_main_loop_run () from /usr/lib/libglib-2.0.so.0
#10 0x408f9423 in gtk_main () from /usr/lib/libgtk-x11-2.0.so.0
#11 0x40647899 in Gtk::Main::run_impl() (this=0xbffff400) at main.cc:470
#12 0x406475a4 in Gtk::Main::run() () at main.cc:417
#13 0x08308eb3 in main (argc=0, argv=0xbffff494) at main.cpp:83
#14 0x4a7be90c in __libc_start_main () from /lib/libc.so.6

------- You are receiving this mail because: -------
You are the assignee for the bug.


--__--__--

Message: 2
From: bugzilla-daemon bugzilla gnome org
To: gtkmm-forge lists sourceforge net
Cc: 
Date: Wed, 12 Jan 2005 01:39:04 -0500 (EST)
Subject: [gtkmm bugzilla] [Bug 163765] Glib::Dispatcher crash

Please DO NOT reply to this by email. All additional comments should be made in
the comments box of this bug report.

 http://bugzilla.gnome.org/show_bug.cgi?id=163765
 glibmm | threads | Ver: 2.4.x





------- Additional Comments From Robert Quattlebaum, Jr.  2005-01-12 01:39 -------
A suitable work-around is to use Glib::signal_timeout() with a timeout value of zero, and binding the 
return value of the slot to "false".

This seems to work rather well in my code.

------- You are receiving this mail because: -------
You are the assignee for the bug.


--__--__--

Message: 3
From: bugzilla-daemon bugzilla gnome org
To: gtkmm-forge lists sourceforge net
Cc: 
Date: Wed, 12 Jan 2005 06:57:15 -0500 (EST)
Subject: [gtkmm bugzilla] [Bug 140515] Container child properties not wrapped

Please DO NOT reply to this by email. All additional comments should be made in
the comments box of this bug report.

 http://bugzilla.gnome.org/show_bug.cgi?id=140515
 gtkmm | general | Ver: 2.4

Kjartan Maraas changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
      everconfirmed|0                           |1



------- You are receiving this mail because: -------
You are the assignee for the bug.



--__--__--

_______________________________________________
Gtkmm-forge mailing list
Gtkmm-forge lists sourceforge net
https://lists.sourceforge.net/lists/listinfo/gtkmm-forge


End of Gtkmm-forge Digest