[gtkmm] Gtkmm-forge digest, Vol 1 #711 - 1 msg

[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 144420] New:  - Segfault in libsigc++ (bugzilla-daemon bugzilla gnome org)

--__--__--

Message: 1
From: bugzilla-daemon bugzilla gnome org
To: gtkmm-forge lists sourceforge net
Cc: 
Date: Tue, 15 Jun 2004 09:43:08 -0400 (EDT)
Subject: [gtkmm bugzilla] [Bug 144420] New:  - Segfault in libsigc++

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

           Summary: Segfault in libsigc++
           Product: glibmm
           Version: 2.4.x
          Platform: Other
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: major
          Priority: Normal
         Component: general
        AssignedTo: gtkmm-forge lists sourceforge net
        ReportedBy: morten wtf dk


My application has started to segfault with latest glibmm and libsigc++. A
backtrace with debug symbols from libraries looks like this:

Program received signal SIGSEGV, Segmentation fault.
0x082530da in ?? ()
(gdb) bt
#0  0x082530da in ?? ()
#1  0x40666be0 in ~slot_base (this=0x822aee0) at slot_base.h:87
#2  0x406465b4 in (anonymous
namespace)::SourceConnectionNode::destroy_notify_callback (data=0x822aee0) at
main.cc:72
#3  0x407b6818 in g_source_set_callback_indirect ()
   from /usr/lib/libglib-2.0.so.0
#4  0x407b798d in g_main_depth () from /usr/lib/libglib-2.0.so.0
#5  0x407b8a38 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#6  0x407b8d70 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#7  0x407b93b3 in g_main_loop_run () from /usr/lib/libglib-2.0.so.0
#8  0x40440d13 in gtk_main () from /usr/lib/libgtk-x11-2.0.so.0
#9  0x4018d4e9 in Gtk::Main::run_impl () from /usr/lib/libgtkmm-2.4.so.1
#10 0x4018d333 in Gtk::Main::run () from /usr/lib/libgtkmm-2.4.so.1
#11 0x0809b232 in main (argc=2, argv=0xbffff9f4) at main.cpp:48

slot_base.h (libsigc++) line 87 gives me this:

  inline ~slot_rep()
    { if (detach_) (*detach_)(this); }

main.cc (glibmm) line 72 gives me this:

  if (self->source_)
  {
    GSource* s = self->source_;
    self->source_ = 0;
    g_source_destroy(s);

    delete self; // <-- line 72
  }

Unfortunately, I havn't had success in providing a simple reproducable example
of application code.

------- 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