Hello Kjell, you are right but for now I do not have more info :(. If I get more info or a way to reproduce it in an easy way I will tell you.
Thanks!! 2016-12-16 16:54 GMT+01:00 Kjell Ahlstedt <kjell.ahlst...@bredband.net>: > Den 2016-12-16 kl. 13:25, skrev Miguel París Díaz: > > Hello, > I have noticed that sometimes I get SIGSEGV in: > sigc::internal::signal_emit1 (/usr/include/sigc++-2.0/sigc+ > +/signal.h:1004) > > I am using the next version: > ii libsigc++-2.0-dev:amd64 2.6.2-1 > > It his fixed in a greater version? > > Thanks in advance!! > > -- > Miguel París Díaz > ------------------------------------------------------------------------ > Computer/Software engineer. > Researcher and architect in <http://www.kurento.org>http://www.kurento.org > http://twitter.com/mparisdiaz > ------------------------------------------------------------------------ > > It's not possible to answer your question without more information. When > does the segfault happen? In what program? The bug could be in libsigc++, > like you suspect, or it could be in the code that uses libsigc++. It's > impossible to tell from your short description. If you can supply a small > test case, it would probably be easy to tell where the bug is, and whether > it has been fixed. > > Kjell > -- Miguel París Díaz ------------------------------------------------------------------------ Computer/Software engineer. Researcher and architect in http://www.kurento.org http://twitter.com/mparisdiaz ------------------------------------------------------------------------
_______________________________________________ libsigc-list mailing list libsigc-list@gnome.org https://mail.gnome.org/mailman/listinfo/libsigc-list
