GNOME.org
 

Gtkmm-forge digest, Vol 1 #1002 - 5 msgs

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 154498] Unnecessary warning on console: signalproxy_connectionnode.cc (glibmm (bugzilla.gnome.org))
   2. [Bug 315874] GObject wrapper is considered destroyed too soon (glibmm (bugzilla.gnome.org))
   3. [Bug 321552] Double entries in trackable list when binding a slot to a slot (libsigc++ (bugzilla.gnome.org))
   4. [Bug 321552] Double entries in trackable list when binding a slot to a slot (libsigc++ (bugzilla.gnome.org))
   5. [Bug 321776] compile errors with glib from cvs (glibmm (bugzilla.gnome.org))

--__--__--

Message: 1
From: "glibmm (bugzilla.gnome.org)" <bugzilla-daemon bugzilla gnome org>
To: gtkmm-forge lists sourceforge net
Date: Fri, 18 Nov 2005 23:57:37 -0500 (EST)
Subject: [gtkmm bugzilla] [Bug 154498] Unnecessary warning on console: signalproxy_connectionnode.cc

Do not reply to this via email (we are currently unable to handle email
responses and they get discarded).  You can add comments to this bug at
http://bugzilla.gnome.org/show_bug.cgi?id=3D154498
 glibmm | general | Ver: 2.4.x

R=E9gis Duchesne changed:

           What    |Removed                     |Added
-------------------------------------------------------------------------=
---
                 CC|                            |hpreg vmware com



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


--__--__--

Message: 2
From: "glibmm (bugzilla.gnome.org)" <bugzilla-daemon bugzilla gnome org>
To: gtkmm-forge lists sourceforge net
Date: Sat, 19 Nov 2005 00:06:44 -0500 (EST)
Subject: [gtkmm bugzilla] [Bug 315874] GObject wrapper is considered destroyed too soon

Do not reply to this via email (we are currently unable to handle email
responses and they get discarded).  You can add comments to this bug at
http://bugzilla.gnome.org/show_bug.cgi?id=3D315874
 glibmm | object | Ver: 2.8.x

R=E9gis Duchesne changed:

           What    |Removed                     |Added
-------------------------------------------------------------------------=
---
                 CC|                            |hpreg vmware com



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


--__--__--

Message: 3
From: "libsigc++ (bugzilla.gnome.org)" <bugzilla-daemon bugzilla gnome org>
To: gtkmm-forge lists sourceforge net
Date: Sat, 19 Nov 2005 00:10:19 -0500 (EST)
Subject: [gtkmm bugzilla] [Bug 321552] Double entries in trackable list when binding a slot to a slot

Do not reply to this via email (we are currently unable to handle email
responses and they get discarded).  You can add comments to this bug at
http://bugzilla.gnome.org/show_bug.cgi?id=3D321552
 libsigc++ | adaptors | Ver: 2.0.x

R=E9gis Duchesne changed:

           What    |Removed                     |Added
-------------------------------------------------------------------------=
---
                 CC|                            |hpreg vmware com



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


--__--__--

Message: 4
From: "libsigc++ (bugzilla.gnome.org)" <bugzilla-daemon bugzilla gnome org>
To: gtkmm-forge lists sourceforge net
Date: Sat, 19 Nov 2005 02:05:43 -0500 (EST)
Subject: [gtkmm bugzilla] [Bug 321552] Double entries in trackable list when binding a slot to a slot

Do not reply to this via email (we are currently unable to handle email
responses and they get discarded).  You can add comments to this bug at
http://bugzilla.gnome.org/show_bug.cgi?id=3D321552
 libsigc++ | adaptors | Ver: 2.0.x





------- Additional Comments From R=E9gis Duchesne  2005-11-19 07:05 -----=
--
Philip,

The only difference I can see between the normal and workaround cases is:

o In the normal case, storage for the bound slot is allocated on the stac=
k (it
is pushed) right before the call to bind(), and it is freed (it is poped)=
 right
after the call to bind(). So the storage does not exist anymore at the ti=
me
'foo' is deleted.

o In the workaround case, storage for the bound slot ('two') is allocated=
 on the
stack upon entering main(). So the storage still exists at the time 'foo'=
 is
deleted.

Valgrind is not perfect: it only knows about accesses to the address spac=
e, it
does not know when objects are constructed or destructed.

I believe that the bug actually happens in _both_ cases, but it is only d=
etected
by valgrind in the normal case (where a memory access occurs beyond the e=
nd of
the stack), and it is not detected in the workaround case (where a memory=
 access
occurs inside the stack, so it appears valid to valgrind although it happ=
ens
after the object that was stored there has been destructed).

In other words, I don't think the workaround case is an actual workaround=
. I
wanted to verify this theory by myself, by crafting a more careful workar=
ound
case: allocate 'two' on the _heap_ right before the call to bind(), then =
delete
it after the call to bind(). I believe this will help valgrind detect the
problem even in the "workaround" case.

Unfortunately, I'm unable to reproduce the problem on my system (which us=
es gcc
4.0.3) under valgrind, i.e. there is nothing after the "DoFoo" line in
valgrind's output. Can you please verify my theory on your system?


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


--__--__--

Message: 5
From: "glibmm (bugzilla.gnome.org)" <bugzilla-daemon bugzilla gnome org>
To: gtkmm-forge lists sourceforge net
Date: Sat, 19 Nov 2005 06:51:03 -0500 (EST)
Subject: [gtkmm bugzilla] [Bug 321776] compile errors with glib from cvs

Do not reply to this via email (we are currently unable to handle email
responses and they get discarded).  You can add comments to this bug at
http://bugzilla.gnome.org/show_bug.cgi?id=3D321776
 glibmm | build | Ver: unspecified

Christian Kirbach changed:

           What    |Removed                     |Added
-------------------------------------------------------------------------=
---
           Keywords|                            |build



------- 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
[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]