From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <48FCF86F.3030007@domain.hid> Date: Mon, 20 Oct 2008 23:30:23 +0200 From: Jan Kiszka MIME-Version: 1.0 References: <48FCDC52.1070507@domain.hid> <48FCE40C.1080100@domain.hid> <48FCEB70.7030808@domain.hid> <48FCEC25.2040200@domain.hid> <48FCED48.5050608@domain.hid> <48FCF14C.8050103@domain.hid> <48FCF2E2.8050809@domain.hid> <48FCF4FB.1040104@domain.hid> <48FCF74E.1090102@domain.hid> In-Reply-To: <48FCF74E.1090102@domain.hid> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig157C512464693A9AB0C3B9B9" Sender: jan.kiszka@domain.hid Subject: Re: [Xenomai-core] Warning when compiling trunk. List-Id: "Xenomai life and development \(bug reports, patches, discussions\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Gilles Chanteperdrix Cc: Xenomai core This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig157C512464693A9AB0C3B9B9 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Gilles Chanteperdrix wrote: > Jan Kiszka wrote: >> Gilles Chanteperdrix wrote: >>> Gilles Chanteperdrix wrote: >>>> Jan Kiszka wrote: >>>>> Gilles Chanteperdrix wrote: >>>>>> Gilles Chanteperdrix wrote: >>>>>>> Jan Kiszka wrote: >>>>>>>> Gilles Chanteperdrix wrote: >>>>>>>>> I get this warning when compiling trunk: >>>>>>>>> >>>>>>>>> checking for __thread... rm: cannot remove `conftest1.dir': Is = a directory >>>>>>>>> yes >>>>>>>>> >>>>>>>> That simple, it's a typo in this line: >>>>>>>> >>>>>>>> http://www.rts.uni-hannover.de/xenomai/lxr/source/configure.in?v= =3DSVN-trunk#394 >>>>>>>> >>>>>>>> Also, that rm should be done outside the if block to play safe. >>>>>>> Ok. But once this is fixed, I get a segmentation fault with __thr= ead on >>>>>>> ARM in rt_task_trampoline. I am currently testing the SIGWINCH th= ing, >>>>>>> and if __thread is disabled, there is no segfault. >>>>>> If a #ifdef 0 xeno_set_current, there is no segfault. >>>>>> >>>>> Interesting. What about removing the initial-exec attributes? Is >>>>> __thread otherwise know to work on your platform? >>>> Yes. This is a race condition, the real bug is, IMHO: >>>> __native_self =3D *iargs->task; >>>> When the segfault happens iargs->task is NULL. I suspect you are not= >>>> supposed to use iargs after the __native_task_create syscall. >>> Yes, that was the problem. >> What did you change? Can you explain the why to me? >=20 > Because I guess iargs is no longer valid at this point. So, I saved the= > task pointer and reused it. >=20 Sorry, makes no sense to me: *iargs is on the stack of the rt_task_create caller, and that one is not expected to proceed until we issue __xn_sys_barrier. Jan --------------enig157C512464693A9AB0C3B9B9 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.8 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkj8+G8ACgkQniDOoMHTA+nVLACbB5lWfqNe7R7quaCmhDC2Hni+ Xy0An3SOprq/Fav7JfS7Stbv7CQGb56B =YqNa -----END PGP SIGNATURE----- --------------enig157C512464693A9AB0C3B9B9--