GNOME.org
 

Gtkmm-forge Digest, Vol 37, Issue 13

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-owner 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 586626] Clipboard::wait_for_targets() returns	list
      pointing to free'd memory (gtkmm (bugzilla.gnome.org))
   2. [Bug 396958] Glib::signal_idle().connect() not	thread-safe
      (glibmm (bugzilla.gnome.org))
   3. [Bug 512348] Glib::Thread::create() does not	appear to be
      thread safe (glibmm (bugzilla.gnome.org))
   4. [Bug 396958] Glib::signal_idle().connect() not	thread-safe
      (glibmm (bugzilla.gnome.org))
   5. [Bug 396963] Add Glib::signal_idle().connect_once()
      (glibmm (bugzilla.gnome.org))
   6. [Bug 512348] Glib::Thread::create() does not	appear to be
      thread safe (glibmm (bugzilla.gnome.org))
   7. [Bug 396958] Glib::signal_idle().connect() not	thread-safe
      (glibmm (bugzilla.gnome.org))
   8. [Bug 396958] Glib::signal_idle().connect() not	thread-safe
      (glibmm (bugzilla.gnome.org))


----------------------------------------------------------------------

Message: 1
Date: Mon, 22 Jun 2009 13:35:17 +0000 (UTC)
From: "gtkmm (bugzilla.gnome.org)"
	<bugzilla-daemon bugzilla gnome org>
Subject: [gtkmm bugzilla] [Bug 586626] Clipboard::wait_for_targets()
	returns	list pointing to free'd memory
To: gtkmm-forge lists sourceforge net
Message-ID: <20090622133518 59B0223F5B4 label gnome org>
Content-Type: text/plain; charset=utf-8

If you have any questions why you received this email, please see the text at
the end of this email. Replies to this email are NOT read, please see the text
at the end of this email. You can add comments to this bug at:
  http://bugzilla.gnome.org/show_bug.cgi?id=586626

  gtkmm | general | Ver: 2.16.x

Murray Cumming changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |murrayc murrayc com




------- Comment #2 from Murray Cumming  2009-06-22 13:35 UTC -------
Yes, the patch is probably appropriate. CCing Daniel Elstner though, because he
probably has an opinion about this.


-- 
See http://bugzilla.gnome.org/page.cgi?id=email.html for more info about why you received
this email, why you can't respond via email, how to stop receiving
emails (or reduce the number you receive), and how to contact someone
if you are having problems with the system.

You can add comments to this bug at http://bugzilla.gnome.org/show_bug.cgi?id=586626.



------------------------------

Message: 2
Date: Mon, 22 Jun 2009 13:51:37 +0000 (UTC)
From: "glibmm (bugzilla.gnome.org)"
	<bugzilla-daemon bugzilla gnome org>
Subject: [gtkmm bugzilla] [Bug 396958] Glib::signal_idle().connect()
	not	thread-safe
To: gtkmm-forge lists sourceforge net
Message-ID: <20090622135137 56B7E23F5AA label gnome org>
Content-Type: text/plain; charset=utf-8

If you have any questions why you received this email, please see the text at
the end of this email. Replies to this email are NOT read, please see the text
at the end of this email. You can add comments to this bug at:
  http://bugzilla.gnome.org/show_bug.cgi?id=396958

  glibmm | main loop | Ver: 2.13.x




------- Comment #7 from Daniel Elstner  2009-06-22 13:51 UTC -------
Update:

A method connect_once() was been proposed to solve this problem and is now part
of glibmm. Unfortunately, the implementation of connect_once() does not appear
to take the memory visibility problem into account at all. That is, right now
it doesn't solve the problem which led to it being proposed in the first place.


-- 
See http://bugzilla.gnome.org/page.cgi?id=email.html for more info about why you received
this email, why you can't respond via email, how to stop receiving
emails (or reduce the number you receive), and how to contact someone
if you are having problems with the system.

You can add comments to this bug at http://bugzilla.gnome.org/show_bug.cgi?id=396958.



------------------------------

Message: 3
Date: Mon, 22 Jun 2009 13:43:19 +0000 (UTC)
From: "glibmm (bugzilla.gnome.org)"
	<bugzilla-daemon bugzilla gnome org>
Subject: [gtkmm bugzilla] [Bug 512348] Glib::Thread::create() does not
	appear to be thread safe
To: gtkmm-forge lists sourceforge net
Message-ID: <20090622134319 8595323F5A9 label gnome org>
Content-Type: text/plain; charset=utf-8

If you have any questions why you received this email, please see the text at
the end of this email. Replies to this email are NOT read, please see the text
at the end of this email. You can add comments to this bug at:
  http://bugzilla.gnome.org/show_bug.cgi?id=512348

  glibmm | threads | Ver: 2.14.x

Daniel Elstner changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |daniel kitta gmail com




------- Comment #15 from Daniel Elstner  2009-06-22 13:43 UTC -------
Wait a moment -- can't you just *not derive* your class from sigc::trackable
and that's it?  There used to be a class_slot()  in older versions of sigc++,
but I think since the switch to the boost syntax it is now implicitly untracked
if the object does not derive from trackable.


-- 
See http://bugzilla.gnome.org/page.cgi?id=email.html for more info about why you received
this email, why you can't respond via email, how to stop receiving
emails (or reduce the number you receive), and how to contact someone
if you are having problems with the system.

You can add comments to this bug at http://bugzilla.gnome.org/show_bug.cgi?id=512348.



------------------------------

Message: 4
Date: Mon, 22 Jun 2009 13:56:43 +0000 (UTC)
From: "glibmm (bugzilla.gnome.org)"
	<bugzilla-daemon bugzilla gnome org>
Subject: [gtkmm bugzilla] [Bug 396958] Glib::signal_idle().connect()
	not	thread-safe
To: gtkmm-forge lists sourceforge net
Message-ID: <20090622135643 D1B5223F5A5 label gnome org>
Content-Type: text/plain; charset=utf-8

If you have any questions why you received this email, please see the text at
the end of this email. Replies to this email are NOT read, please see the text
at the end of this email. You can add comments to this bug at:
  http://bugzilla.gnome.org/show_bug.cgi?id=396958

  glibmm | main loop | Ver: 2.13.x

Daniel Elstner changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
  BugsThisDependsOn|                            |396963

Bug 396958 depends on bug 396963, which changed state.

Bug 396963 Summary: Add Glib::signal_idle().connect_once()
http://bugzilla.gnome.org/show_bug.cgi?id=396963

           What    |Old Value                   |New Value
----------------------------------------------------------------------------
             Status|RESOLVED                    |UNCONFIRMED
         Resolution|FIXED                       |



-- 
See http://bugzilla.gnome.org/page.cgi?id=email.html for more info about why you received
this email, why you can't respond via email, how to stop receiving
emails (or reduce the number you receive), and how to contact someone
if you are having problems with the system.

You can add comments to this bug at http://bugzilla.gnome.org/show_bug.cgi?id=396958.



------------------------------

Message: 5
Date: Mon, 22 Jun 2009 13:56:42 +0000 (UTC)
From: "glibmm (bugzilla.gnome.org)"
	<bugzilla-daemon bugzilla gnome org>
Subject: [gtkmm bugzilla] [Bug 396963] Add
	Glib::signal_idle().connect_once()
To: gtkmm-forge lists sourceforge net
Message-ID: <20090622135642 DB27E23F542 label gnome org>
Content-Type: text/plain; charset=utf-8

If you have any questions why you received this email, please see the text at
the end of this email. Replies to this email are NOT read, please see the text
at the end of this email. You can add comments to this bug at:
  http://bugzilla.gnome.org/show_bug.cgi?id=396963

  glibmm | main loop | Ver: 2.13.x

Daniel Elstner changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
OtherBugsDependingO|                            |396958
              nThis|                            |
             Status|RESOLVED                    |UNCONFIRMED
         Resolution|FIXED                       |




------- Comment #8 from Daniel Elstner  2009-06-22 13:56 UTC -------
http://git.gnome.org/cgit/glibmm/tree/glib/glibmm/main.cc#n313

This implementation of connect_once() fails to solve the problem for which it
was originally proposed as a solution.

    void SignalTimeout::connect_once(const sigc::slot<void>& slot, 
                                     unsigned int interval, int priority)
    {
      connect(sigc::bind_return(slot, false), interval, priority);
    }

This has exactly the same problem as before, just moved to the library instead
of the application. Reopening.


-- 
See http://bugzilla.gnome.org/page.cgi?id=email.html for more info about why you received
this email, why you can't respond via email, how to stop receiving
emails (or reduce the number you receive), and how to contact someone
if you are having problems with the system.

You can add comments to this bug at http://bugzilla.gnome.org/show_bug.cgi?id=396963.



------------------------------

Message: 6
Date: Mon, 22 Jun 2009 14:38:30 +0000 (UTC)
From: "glibmm (bugzilla.gnome.org)"
	<bugzilla-daemon bugzilla gnome org>
Subject: [gtkmm bugzilla] [Bug 512348] Glib::Thread::create() does not
	appear to be thread safe
To: gtkmm-forge lists sourceforge net
Message-ID: <20090622143830 334B223F5A9 label gnome org>
Content-Type: text/plain; charset=utf-8

If you have any questions why you received this email, please see the text at
the end of this email. Replies to this email are NOT read, please see the text
at the end of this email. You can add comments to this bug at:
  http://bugzilla.gnome.org/show_bug.cgi?id=512348

  glibmm | threads | Ver: 2.14.x




------- Comment #16 from Chris Vine  2009-06-22 14:38 UTC -------
Comment #15:  Of course, and that is what the documentation patch I submitted
for Glib::Thread::create() (now in glibmm-2.20) says.

However, though now documented, this is a trap for the unwary - trackability
is, or should be, irrelevant to the passing of a slot to start a new thread. 
Rather than document the problem, it would be better to prevent it by
"switching off" trackability for the slot copied to call_thread_entry_slot(). 
This cannot be done at present.


-- 
See http://bugzilla.gnome.org/page.cgi?id=email.html for more info about why you received
this email, why you can't respond via email, how to stop receiving
emails (or reduce the number you receive), and how to contact someone
if you are having problems with the system.

You can add comments to this bug at http://bugzilla.gnome.org/show_bug.cgi?id=512348.



------------------------------

Message: 7
Date: Mon, 22 Jun 2009 15:07:03 +0000 (UTC)
From: "glibmm (bugzilla.gnome.org)"
	<bugzilla-daemon bugzilla gnome org>
Subject: [gtkmm bugzilla] [Bug 396958] Glib::signal_idle().connect()
	not	thread-safe
To: gtkmm-forge lists sourceforge net
Message-ID: <20090622150707 D0C2123EF5D label gnome org>
Content-Type: text/plain; charset=utf-8

If you have any questions why you received this email, please see the text at
the end of this email. Replies to this email are NOT read, please see the text
at the end of this email. You can add comments to this bug at:
  http://bugzilla.gnome.org/show_bug.cgi?id=396958

  glibmm | main loop | Ver: 2.13.x




------- Comment #8 from Chris Vine  2009-06-22 15:06 UTC -------
g_idle_add() itself is thread safe.  According to
http://mail.gnome.org/archives/gtkmm-list/2007-January/msg00145.html , leaving
aside the sigc::trackable issue, all that is now needed is to move the call to
Glib::SourceConnectionNode::install() to before the call to g_source_attach().

There is still the same sigc::trackable point as arises in bug #512348, which
may or may not be a problem, depending on whether you view it only as a
documentation issue.


-- 
See http://bugzilla.gnome.org/page.cgi?id=email.html for more info about why you received
this email, why you can't respond via email, how to stop receiving
emails (or reduce the number you receive), and how to contact someone
if you are having problems with the system.

You can add comments to this bug at http://bugzilla.gnome.org/show_bug.cgi?id=396958.



------------------------------

Message: 8
Date: Mon, 22 Jun 2009 15:23:08 +0000 (UTC)
From: "glibmm (bugzilla.gnome.org)"
	<bugzilla-daemon bugzilla gnome org>
Subject: [gtkmm bugzilla] [Bug 396958] Glib::signal_idle().connect()
	not	thread-safe
To: gtkmm-forge lists sourceforge net
Message-ID: <20090622152308 8D22423F5B0 label gnome org>
Content-Type: text/plain; charset=utf-8

If you have any questions why you received this email, please see the text at
the end of this email. Replies to this email are NOT read, please see the text
at the end of this email. You can add comments to this bug at:
  http://bugzilla.gnome.org/show_bug.cgi?id=396958

  glibmm | main loop | Ver: 2.13.x




------- Comment #9 from Chris Vine  2009-06-22 15:23 UTC -------
On reflection I think my comment #8 is wrong.  There still seems to be an
unused sigc::connection object in existence.  I think the call needs to be
reimplemented rather than rely on sigc::bind_return() and handing it off.


-- 
See http://bugzilla.gnome.org/page.cgi?id=email.html for more info about why you received
this email, why you can't respond via email, how to stop receiving
emails (or reduce the number you receive), and how to contact someone
if you are having problems with the system.

You can add comments to this bug at http://bugzilla.gnome.org/show_bug.cgi?id=396958.



------------------------------

------------------------------------------------------------------------------
Are you an open source citizen? Join us for the Open Source Bridge conference!
Portland, OR, June 17-19. Two days of sessions, one day of unconference: $250.
Need another reason to go? 24-hour hacker lounge. Register today!
http://ad.doubleclick.net/clk;215844324;13503038;v?http://opensourcebridge.org

------------------------------

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


End of Gtkmm-forge Digest, Vol 37, Issue 13
*******************************************
[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]