Re: [gtkmm] Possible bug in SigC::Connection::disconnect()
- From: Martin Schulze <martin-ml hippogriff de>
- To: Ole André Vadla Ravnås <ole ravnas lyse net>
- Cc: gtkmm-list gnome org, libsigc-list gnome org
- Subject: Re: [gtkmm] Possible bug in SigC::Connection::disconnect()
- Date: Mon, 24 Nov 2003 23:19:03 +0100
Am 2003.11.23 23:59 schrieb(en) Ole André Vadla Ravnås:
I think I've encountered a possible bug with the disconnect() method
of
SigC::Connection (after several days of headscratching :-) ) To me it
seems like disconnect() doesn't clean up properly, and causes future
emit()'s on the given signal to make valgrind spew out memory-errors
--
at best, or, worse, which happened in my case under some
circumstances,
results in a crash (segfault).
I assume you made sure you are using the latest release of
libsigc++-1.2?
Could you modify/simplify your test case so that it only uses
libsigc++ (not gtkmm) and open a bug at bugzilla.gnome.org?
The code looks perfectly legal to me.
Regards,
Martin
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]