From: Philippe Gerum <rpm@xenomai.org>
To: Roderik_Wildenburg@domain.hid
Cc: xenomai@xenomai.org
Subject: Re: AW: AW:[Xenomai-help] undefinedreference __xnarch_xchg_called_with_bad_pointer
Date: Wed, 01 Mar 2006 09:03:33 +0100 [thread overview]
Message-ID: <44055555.5050501@domain.hid> (raw)
In-Reply-To: <5D63919D95F87E4D9D34FF7748CE2C2A1C3DF1@domain.hid>
Roderik_Wildenburg@domain.hid wrote:
> Any idea why I don´t get this error when compiling the native examples. Isn´t atomic.h included with these examples too ?
Included yes, but not actually used.
>
>
>>-----Ursprüngliche Nachricht-----
>>Von: xenomai-help-bounces@domain.hid
>>[mailto:xenomai-help-bounces@domain.hid] Im Auftrag von Heikki Lindholm
>>Gesendet: Dienstag, 28. Februar 2006 20:06
>>An: Philippe Gerum
>>Cc: xenomai@xenomai.org
>>Betreff: Re: AW:[Xenomai-help] undefinedreference
>>__xnarch_xchg_called_with_bad_pointer
>>
>>Philippe Gerum kirjoitti:
>>
>>>Heikki Lindholm wrote:
>>>
>>>
>>>>Uh. I guess the compiler isn't killing the *_bad_pointer
>>
>>function as
>>
>>>>dead code when debug is enabled (although it is dead-code.)
>>>
>>>
>>>The optimizer is disabled by --enable-debug so that we don't get
>>>strange jumps while tracing with GDB, I guess that's why
>>
>>the dead code
>>
>>>is not eliminated. What about just killing this check,
>>
>>since the same
>>
>>>code is already validated when compiling it as a kernel module?
>>>(except asm-uvm/system.h, but that's not important).
>>
>>Yep. That seems like the way to go. I don't see much to gain
>>from the check. Of course, paranoid way would be to add the
>>__bad_ptr() function with abort() or something inside. Quick
>>patch attached for the former case.
>>
>>- hl
>>
>
>
--
Philippe.
prev parent reply other threads:[~2006-03-01 8:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-01 7:20 AW: AW:[Xenomai-help] undefinedreference __xnarch_xchg_called_with_bad_pointer Roderik_Wildenburg
2006-03-01 8:03 ` Philippe Gerum [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=44055555.5050501@domain.hid \
--to=rpm@xenomai.org \
--cc=Roderik_Wildenburg@domain.hid \
--cc=xenomai@xenomai.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.