Description of problem: Twinkle crashes right when launched. Performing it via gdb -e `which twinkle` produces: (gdb) bt #0 0x0000003f7bc35ba5 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:63 #1 0x0000003f7bc37358 in __GI_abort () at abort.c:90 #2 0x0000003f7bc7559b in __libc_message (do_abort=do_abort@entry=2, fmt=fmt@entry=0x3f7bd787ff "*** %s ***: %s terminated\n") at ../sysdeps/unix/sysv/linux/libc_fatal.c:197 #3 0x0000003f7bd0a697 in __GI___fortify_fail (msg=msg@entry=0x3f7bd787a5 "buffer overflow detected") at fortify_fail.c:31 #4 0x0000003f7bd08810 in __GI___chk_fail () at chk_fail.c:28 #5 0x0000003f8a028e73 in memset (__len=8, __dest=<optimized out>, __ch=0) at /usr/include/bits/string3.h:84 #6 ost::IPV4Address::setAddress (this=0x3f8a24d320 <ost::IPV4Host::_host_>, host=<optimized out>) at inaddr.cpp:336 #7 0x0000003f8a0295f8 in ost::IPV4Host::IPV4Host (this=0x3f8a24d320 <ost::IPV4Host::_host_>, host=0x0) at inaddr.cpp:257 #8 0x0000003f88a200f1 in __static_initialization_and_destruction_0 (__initialize_p=<optimized out>, __priority=<optimized out>) at address.cpp:80 #9 _GLOBAL__sub_I_address.cpp(void) () at address.cpp:1208 #10 0x0000003f7b80ef36 in call_init (l=l@entry=0x7ffff7fd6998, argc=argc@entry=1, argv=argv@entry=0x7fffffffe148, env=env@entry=0x7fffffffe158) at dl-init.c:82 #11 0x0000003f7b80eff0 in call_init (env=<optimized out>, argv=<optimized out>, argc=<optimized out>, l=0x7ffff7fd6998) at dl-init.c:53 #12 _dl_init (main_map=0x3f7ba222a8, argc=1, argv=0x7fffffffe148, env=0x7fffffffe158) at dl-init.c:131 #13 0x0000003f7b8015ca in _dl_start_user () from /lib64/ld-linux-x86-64.so.2 Version-Release number of selected component (if applicable): twinkle-1.4.2-19.fc18.x86_64 How reproducible: Always - on my laptop. Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
*** This bug has been marked as a duplicate of bug 830175 ***