GNOME.org
 

[gtkmm] Gtkmm-forge digest, Vol 1 #724 - 9 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 143185]  - error in line.h (bugzilla-daemon bugzilla gnome org)
   2. [Bug 137591]  - Build failure when building in a Cygwin/win32 environment (bugzilla-daemon bugzilla gnome org)
   3. [Bug 143185]  - error in line.h (bugzilla-daemon bugzilla gnome org)
   4. [Bug 143185]  - error in line.h (bugzilla-daemon bugzilla gnome org)
   5. [Bug 145571]  - sigc::connection::disconnect() causes crash (bugzilla-daemon bugzilla gnome org)
   6. [Bug 145571]  - sigc::connection::disconnect() causes crash (bugzilla-daemon bugzilla gnome org)
   7. [Bug 145571]  - sigc::connection::disconnect() causes crash (bugzilla-daemon bugzilla gnome org)
   8. [Bug 145571]  - sigc::connection::disconnect() causes crash (bugzilla-daemon bugzilla gnome org)
   9. [Bug 145571]  - sigc::connection::disconnect() causes crash (bugzilla-daemon bugzilla gnome org)

--__--__--

Message: 1
From: bugzilla-daemon bugzilla gnome org
To: gtkmm-forge lists sourceforge net
Cc: 
Date: Fri,  9 Jul 2004 04:31:04 -0400 (EDT)
Subject: [gtkmm bugzilla] [Bug 143185]  - error in line.h

http://bugzilla.gnome.org/show_bug.cgi?id=143185
gnomemm | libgnomecanvasmm | Ver: 2.0





------- Additional Comments From murrayc murrayc com  2004-07-09 04:31 -------
1. You are patching a generated files. Please see this page for help with making
patches:
http://www.gtkmm.org/bugs.shtml#CreatingPatches
Also, please patch the ChangeLog.

2. You seem to be patching libgnomecanvasmm 2.0, and the first comment here
seems to be an error in libgnomecanvasmm 2.0, but then Christian mentions that
he tried  2.6 versions. What branch really has this problem?

------- 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: Fri,  9 Jul 2004 04:36:30 -0400 (EDT)
Subject: [gtkmm bugzilla] [Bug 137591]  - Build failure when building in a Cygwin/win32 environment

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





------- Additional Comments From roger whinlatter uklinux net  2004-07-09 04:36 -------
The glib patches are now in glib 2.4.1+.  I haven't yet had a chance to get the
current stable atk/pango/gtk to build, but the cygnome2 folks at sourceforge are
working on it.  It's certainly not ready to build glibmm/gtkmm etc. yet.

Regards,
Roger

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


--__--__--

Message: 3
From: bugzilla-daemon bugzilla gnome org
To: gtkmm-forge lists sourceforge net
Cc: 
Date: Fri,  9 Jul 2004 04:58:34 -0400 (EDT)
Subject: [gtkmm bugzilla] [Bug 143185]  - error in line.h

http://bugzilla.gnome.org/show_bug.cgi?id=143185
gnomemm | libgnomecanvasmm | Ver: 2.0

ed catmur co uk changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
  Attachment #29368|0                           |1
        is obsolete|                            |



------- Additional Comments From ed catmur co uk  2004-07-09 04:58 -------
Created an attachment (id=29373)
 --> (http://bugzilla.gnome.org/attachment.cgi?id=29373&action=view)
2.0.1-gcc3.4.patch

Sorry. This is the correct patch.
I don't use libgnomecanvasmm 2.6 but I imagine a similar change will be needed
if it hasn't already been fixed. I'll look at it when I have time.

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


--__--__--

Message: 4
From: bugzilla-daemon bugzilla gnome org
To: gtkmm-forge lists sourceforge net
Cc: 
Date: Fri,  9 Jul 2004 05:19:52 -0400 (EDT)
Subject: [gtkmm bugzilla] [Bug 143185]  - error in line.h

http://bugzilla.gnome.org/show_bug.cgi?id=143185
gnomemm | libgnomecanvasmm | Ver: 2.0





------- Additional Comments From ed catmur co uk  2004-07-09 05:19 -------
libgnomecanvasmm 2.6.1 compiles fine without any changes needed on my machine
(using gcc 3.4.1). 
As the original report was about libgnomecanvasmm 2.0 and the patch I posted
fixes that branch this bug can probably be closed.

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


--__--__--

Message: 5
From: bugzilla-daemon bugzilla gnome org
To: gtkmm-forge lists sourceforge net
Cc: 
Date: Fri,  9 Jul 2004 07:26:53 -0400 (EDT)
Subject: [gtkmm bugzilla] [Bug 145571]  - sigc::connection::disconnect() causes crash

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





------- Additional Comments From olau hardworking dk  2004-07-09 07:26 -------
I didn't think of running it inside Valgrind. Good idea. Now it does
not actually crash, but instead I get this when I hit enter twice:

button_clicked
key_event_cb
==2884==
==2884== Invalid read of size 4
==2884==    at 0x3C65FD6A:
Glib::SignalProxyConnectionNode::destroy_notify_handler(void*, _GClosure*) (in
/usr/lib/libglibmm-2.4.so.1.0.3)
==2884==    by 0x3C779274: (within /usr/lib/libgobject-2.0.so.0.400.2)
==2884==    by 0x3C77868D: g_closure_unref (in /usr/lib/libgobject-2.0.so.0.400.2)
==2884==    by 0x3C78E50C: (within /usr/lib/libgobject-2.0.so.0.400.2)
==2884==  Address 0x3D037A30 is 12 bytes inside a block of size 16 free'd
==2884==    at 0x3C01FA3C: operator delete(void*) (vg_replace_malloc.c:129)
==2884==    by 0x3C65FD34: Glib::SignalProxyConnectionNode::notify(void*) (in
/usr/lib/libglibmm-2.4.so.1.0.3)
==2884==    by 0x3C67C9E7: sigc::internal::slot_rep::disconnect() (in
/usr/lib/libsigc-2.0.so.0.0.0)
==2884==    by 0x3C67CDFB: sigc::slot_base::disconnect() (in
/usr/lib/libsigc-2.0.so.0.0.0)


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


--__--__--

Message: 6
From: bugzilla-daemon bugzilla gnome org
To: gtkmm-forge lists sourceforge net
Cc: 
Date: Fri,  9 Jul 2004 08:22:59 -0400 (EDT)
Subject: [gtkmm bugzilla] [Bug 145571]  - sigc::connection::disconnect() causes crash

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





------- Additional Comments From murrayc murrayc com  2004-07-09 08:22 -------
> The crash occurs if you start the program and press enter a couple of times
(say four or five)

Now, I see what you mean.

Strangely, it crashes for me in my built-from-source environment, but not when
I'm using the debian packages (all unstable + the gtkmm package from testing). 

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


--__--__--

Message: 7
From: bugzilla-daemon bugzilla gnome org
To: gtkmm-forge lists sourceforge net
Cc: 
Date: Fri,  9 Jul 2004 08:41:57 -0400 (EDT)
Subject: [gtkmm bugzilla] [Bug 145571]  - sigc::connection::disconnect() causes crash

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

murrayc murrayc com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
  Attachment #29319|0                           |1
        is obsolete|                            |



------- Additional Comments From murrayc murrayc com  2004-07-09 08:41 -------
Created an attachment (id=29377)
 --> (http://bugzilla.gnome.org/attachment.cgi?id=29377&action=view)
test_simpler.cc

Here (test_simpler.cc) is a simpler test case. Even if it doesn't crash, it
shows the error in valgrind, and that's what we need to deal with.

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


--__--__--

Message: 8
From: bugzilla-daemon bugzilla gnome org
To: gtkmm-forge lists sourceforge net
Cc: 
Date: Fri,  9 Jul 2004 11:12:45 -0400 (EDT)
Subject: [gtkmm bugzilla] [Bug 145571]  - sigc::connection::disconnect() causes crash

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





------- Additional Comments From murrayc murrayc com  2004-07-09 11:12 -------
The valgrind output:

==29323==
==29323== Invalid read of size 4
==29323==    at 0x3C643D9A:
Glib::SignalProxyConnectionNode::destroy_notify_handler(void*, _GClosure*)
(signalproxy_connectionnode.cc:73)
==29323==    by 0x3C75B984: closure_invoke_notifiers (gclosure.c:109)
==29323==    by 0x3C75AD9D: g_closure_unref (gclosure.c:347)
==29323==    by 0x3C770C1C: handler_unref_R (gsignal.c:590)
==29323==    by 0x3C76EFF4: signal_emit_unlocked_R (gsignal.c:2567)
==29323==    by 0x3C76E326: g_signal_emit_valist (gsignal.c:2195)
==29323==    by 0x3C76E623: g_signal_emit (gsignal.c:2239)
==29323==    by 0x3C3818B4: gtk_button_clicked (gtkbutton.c:719)
==29323==    by 0x3C3828CA: gtk_real_button_released (gtkbutton.c:1220)
==29323==    by 0x3C14F358: Gtk::Button_Class::released_callback(_GtkButton*)
(button.cc:219)
==29323==    by 0x3C76F860: g_cclosure_marshal_VOID__VOID (gmarshal.c:77)
==29323==    by 0x3C75B6C6: g_type_class_meta_marshal (gclosure.c:514)
==29323==    by 0x3C75B32F: g_closure_invoke (gclosure.c:437)
==29323==    by 0x3C76EB8D: signal_emit_unlocked_R (gsignal.c:2366)
==29323==    by 0x3C76E326: g_signal_emit_valist (gsignal.c:2195)
==29323==    by 0x3C76E623: g_signal_emit (gsignal.c:2239)
==29323==    by 0x3C381804: gtk_button_released (gtkbutton.c:711)
==29323==    by 0x3C38274A: gtk_button_button_release (gtkbutton.c:1136)
==29323==    by 0x3C1F5371:
Gtk::Widget_Class::button_release_event_callback(_GtkWidget*, _GdkEventButton*)
(widget.cc:3798)
==29323==    by 0x3C43D603: _gtk_marshal_BOOLEAN__BOXED (gtkmarshalers.c:82)
==29323==  Address 0x3CFC8D70 is 12 bytes inside a block of size 16 free'd
==29323==    at 0x3C01FA3C: operator delete(void*) (vg_replace_malloc.c:129)
==29323==    by 0x3C643D64: Glib::SignalProxyConnectionNode::notify(void*)
(signalproxy_connectionnode.cc:60)
==29323==    by 0x3C661A77: sigc::internal::slot_rep::disconnect() (slot_base.cc:37)
==29323==    by 0x3C661E8B: sigc::slot_base::disconnect() (slot_base.cc:142)
==29323==    by 0x3C6619AB: sigc::connection::disconnect() (connection.cc:83)
==29323==    by 0x804DDE6: Test::button_clicked() (in /home/murrayc/a.out)
==29323==    by 0x804E3C8: sigc::bound_mem_functor0<void, Test>::operator()()
const (in /home/murrayc/a.out)
==29323==    by 0x804E253: sigc::adaptor_functor<sigc::bound_mem_functor0<void,
Test> >::operator()() const (in /home/murrayc/a.out)
==29323==    by 0x804E23D:
sigc::internal::slot_call0<sigc::bound_mem_functor0<void, Test>,
void>::call_it(sigc::internal::slot_rep*) (in /home/murrayc/a.out)
==29323==    by 0x3C643BDC:
Glib::SignalProxyNormal::slot0_void_callback(_GObject*, void*) (slot.h:426)
==29323==    by 0x3C76F860: g_cclosure_marshal_VOID__VOID (gmarshal.c:77)
==29323==    by 0x3C75B32F: g_closure_invoke (gclosure.c:437)
==29323==    by 0x3C76F1E4: signal_emit_unlocked_R (gsignal.c:2506)
==29323==    by 0x3C76E326: g_signal_emit_valist (gsignal.c:2195)
==29323==    by 0x3C76E623: g_signal_emit (gsignal.c:2239)
==29323==    by 0x3C3818B4: gtk_button_clicked (gtkbutton.c:719)
==29323==    by 0x3C3828CA: gtk_real_button_released (gtkbutton.c:1220)
==29323==    by 0x3C14F358: Gtk::Button_Class::released_callback(_GtkButton*)
(button.cc:219)
==29323==    by 0x3C76F860: g_cclosure_marshal_VOID__VOID (gmarshal.c:77)
==29323==    by 0x3C75B6C6: g_type_class_meta_marshal (gclosure.c:514)




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


--__--__--

Message: 9
From: bugzilla-daemon bugzilla gnome org
To: gtkmm-forge lists sourceforge net
Cc: 
Date: Fri,  9 Jul 2004 17:12:07 -0400 (EDT)
Subject: [gtkmm bugzilla] [Bug 145571]  - sigc::connection::disconnect() causes crash

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





------- Additional Comments From murrayc murrayc com  2004-07-09 17:12 -------
This might be caused by the fact that destroy_notify callbacks are not called
during GTK+ signal disconnection if the callback is running - destroy_notify
callbacks are then called after the callback has returned.

I'm working on a patch.

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