From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?UTF-8?B?VG9yYWxmIEbDtnJzdGVy?= Subject: trinity cores in watchdog while syslog'ing Date: Wed, 06 Aug 2014 20:16:27 +0200 Message-ID: <53E270FB.8040900@gmx.de> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Return-path: Sender: trinity-owner@vger.kernel.org List-ID: Content-Type: text/plain; charset="us-ascii" To: trinity@vger.kernel.org Just FWIW : Fuzzying a 32 bit Gentoo Linux let the trinity process in side the UML guest sometimes core dump with this back trace: Core was generated by `trinity -C 4 -N 100000 -x mremap -q'. Program terminated with signal 11, Segmentation fault. #0 __GI__IO_fflush (fp=0x8154200) at iofflush.c:40 40 iofflush.c: No such file or directory. (gdb) bt #0 __GI__IO_fflush (fp=0x8154200) at iofflush.c:40 #1 0x080582c3 in synclogs () at log.c:163 #2 0x0805e93d in watchdog () at watchdog.c:363 #3 init_watchdog () at watchdog.c:430 #4 0x080538d9 in main (argc=8, argv=0xbfc8fd94) at trinity.c:132 (gdb) quit -- Toralf