[gtkmm] Gtkmm-forge digest, Vol 1 #747 - 2 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 109966]  - Dispatcher does not work on win32 (bugzilla-daemon bugzilla gnome org)
   2. [Bug 109966]  - Dispatcher does not work on win32 (bugzilla-daemon bugzilla gnome org)

--__--__--

Message: 1
From: bugzilla-daemon bugzilla gnome org
To: gtkmm-forge lists sourceforge net
Cc: 
Date: Tue, 10 Aug 2004 04:19:19 -0400 (EDT)
Subject: [gtkmm bugzilla] [Bug 109966]  - Dispatcher does not work on win32

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





------- Additional Comments From cgustin ibelgique com  2004-08-10 04:19 -------
I found the bug in the dispatcher.cc example.  It is related to the use of
auto_ptr. In the on_progress_finish method, a ThreadProgress pointer was removed
from progress_list_ AND the corresponding object was deleted, which caused some
kind of race condition on win32.

To solve this problem, I removed the auto_ptr's. RefPtr's to the ThreadProgress
objects are now stored in a separate list (progress_ref_list_), which means that
the ThreadProgress objects are deleted when the Application destructor is
called. I think this is also a nice example of a RefPtr used with a non
Glib::Object (see the reference and unreference methods in ThreadProgress).

dispatcher now runs fine on win32, without memory leak.

If somebody could have a look at the code, test it on linux and comment...

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


--__--__--

Message: 2
From: bugzilla-daemon bugzilla gnome org
To: gtkmm-forge lists sourceforge net
Cc: 
Date: Tue, 10 Aug 2004 04:20:47 -0400 (EDT)
Subject: [gtkmm bugzilla] [Bug 109966]  - Dispatcher does not work on win32

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





------- Additional Comments From cgustin ibelgique com  2004-08-10 04:20 -------
Created an attachment (id=30390)
 --> (http://bugzilla.gnome.org/attachment.cgi?id=30390&action=view)
Fixes crash of dispatcher example on win32


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



--__--__--

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


End of Gtkmm-forge Digest