From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <4F509C26.7070308@domain.hid> Date: Fri, 02 Mar 2012 11:08:38 +0100 From: Gilles Chanteperdrix MIME-Version: 1.0 References: <4F3AAA52.6060802@domain.hid> <4F46C7CD.1070509@domain.hid> <4F4920DE.40600@domain.hid> <4F509B3C.9030105@domain.hid> In-Reply-To: <4F509B3C.9030105@domain.hid> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Subject: Re: [Xenomai-help] Freeze while running examples List-Id: Help regarding installation and common use of Xenomai List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: =?UTF-8?B?T3NjYXIgRMOhdmlsYQ==?= Cc: xenomai@xenomai.org On 03/02/2012 11:04 AM, Gilles Chanteperdrix wrote: > On 03/01/2012 05:23 AM, Oscar D=C3=A1vila wrote: >> Finally i could get the dump >> >> >> post-prompt >> No breakpoints or watchpoints. >> >> breakpoints-table-end >> >> post-prompt >> Dump of assembler code for function __ipipe_sync_stage: >> 0xc106d376 <__ipipe_sync_stage+0>: push %ebp >> (...) >> 0xc106d526 <__ipipe_sync_stage+432>: ret >> End of assembler dump. >=20 > The address where the EIP is when the NMI watchdog triggers is > 0xc106d5e1, so, outside this code. >=20 And this dump does not seem to correspond to the kernel that was running when the bug happened, because in that case we had 0xc106d5e1 =3D=3D __ipipe_sync_stage + 0x21b whereas in your dump, __ipipe_sync_stage + 0x21b =3D=3D 0xc106d591 --=20 Gilles.