From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <51AF06FB.6020707@xenomai.org> Date: Wed, 05 Jun 2013 11:38:03 +0200 From: Philippe Gerum MIME-Version: 1.0 References: <51AEF0A5.6010402@xenomai.org> <51AEF87A.8060506@xenomai.org> In-Reply-To: <51AEF87A.8060506@xenomai.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [Xenomai] [xenomai-forge] psos: crash while stressing event timers List-Id: Discussions about the Xenomai project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Ronny Meeus Cc: xenomai@xenomai.org On 06/05/2013 10:36 AM, Philippe Gerum wrote: > On 06/05/2013 10:28 AM, Ronny Meeus wrote: > >> the testcode is attached to the initial mail. >> The issue can be reproduced in all kinds of environments. >> > > Ok, I overlooked the link. I'll have a look and let you know, thanks. > I can reproduce this bug as well, at least a bug with the same symptoms. Using host libthread_db library "/lib64/libthread_db.so.1". Core was generated by `./settime --cpu-affinity=0,1,2 --silent -s -t 1 -b 30 -o 1'. Program terminated with signal 11, Segmentation fault. #0 malloc_consolidate (av=av@entry=0x7f6f7c000020) at malloc.c:4143 4143 unlink(av, p, bck, fwd); (gdb) bt #0 malloc_consolidate (av=av@entry=0x7f6f7c000020) at malloc.c:4143 #1 0x0000003d7147c988 in _int_free (av=0x7f6f7c000020, p=0x7f6f7c000990, have_lock=0) at malloc.c:4043 #2 0x00007f6fe6d14f3a in pvfree (ptr=0x7f6f7c0009a0) at /home/rpm/git/xenomai-forge/include/copperplate/heapobj.h:156 #3 0x00007f6fe6d15062 in delete_timer (tm=0x7f6f7c0009a0) at /home/rpm/git/xenomai-forge/lib/psos/tm.c:67 #4 0x00007f6fe6d150d5 in post_event_once (tmobj=0x7f6f7c0009b8) at /home/rpm/git/xenomai-forge/lib/psos/tm.c:80 #5 0x00007f6fe6adbd99 in timerobj_server (arg=0x0) at /home/rpm/git/xenomai-forge/lib/copperplate/timerobj.c:205 #6 0x0000003d71c07d15 in start_thread (arg=0x7f6fe67a3700) at pthread_create.c:308 #7 0x0000003d714f248d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:114 (gdb) q However, I have to allow multiple CPUs for running the test, pinning it with --cpu-affinity on a single processor papers over the issue it seems. Ok, digging it. -- Philippe.