From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <4ACE0018.20705@domain.hid> Date: Thu, 08 Oct 2009 17:07:04 +0200 From: Gilles Chanteperdrix MIME-Version: 1.0 References: <1255014185.4690.56.camel@domain.hid> In-Reply-To: <1255014185.4690.56.camel@domain.hid> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [Xenomai-help] rt_print segfault on program termination List-Id: Help regarding installation and common use of Xenomai List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Christoph Permes Cc: xenomai@xenomai.org Christoph Permes wrote: > Hi, > > We use a vmware virtual machine for simulation and testing our realtime > applications. > Every time when a realtime application terminates the following core > dump occures: > > Program terminated with signal 11, Segmentation fault. > [New process 11728] > [New process 11726] > [New process 11727] > #0 0xb7e3e675 in free () from /lib/libc.so.6 > (gdb) bt > #0 0xb7e3e675 in free () from /lib/libc.so.6 > #1 0xb80551dd in cleanup_buffer (buffer=0x81dd210) at rt_print.c:350 > #2 0xb7dbee27 in __nptl_deallocate_tsd () from /lib/libpthread.so.0 > #3 0xb7dbff49 in start_thread () from /lib/libpthread.so.0 > #4 0xb7e9cb6e in clone () from /lib/libc.so.6 > > The line where the segfault occures is > free(buffer->ring); > > The segfault never happens when running on a real machine, so it's no > problem when running in production, but it is annoying when every run in > the test environment leads to a segmentation fault. > > Maybe it is a timing related issue as there are no problems on a real > machine. Did you found the issue that was causing segmentation faults, or did you keep your workaround? -- Gilles