All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@domain.hid>
To: Jeff Webb <jeff.webb@domain.hid>
Cc: xenomai@xenomai.org
Subject: Re: Fw: [Fwd: Re: [Xenomai-help] invalid use of FPU in Xenomai context]
Date: Wed, 20 Sep 2006 12:27:45 +0200	[thread overview]
Message-ID: <451117A1.50500@domain.hid> (raw)
In-Reply-To: <20060916042719.M57867@domain.hid>

[-- Attachment #1: Type: text/plain, Size: 759 bytes --]

Jeff Webb wrote:
> ...
> /* Real-time task */
> void * fptest_routine (void *cookie)
> {  
>   struct timespec dt_ts;
> 
>   int i;
>   char c[6000];

[Those are the days when you wonder why you don't look at the code
*first* and *then* decide to fire up a debugger. Well, at least the
debugger is now debugged too...]

As this disassembly from fptest_routine popped up in ddd

0xd08a511c:     sub    $0x1780,%esp

I wondered why the stack pointer is moved that much. It's because of
that char array above! You have to keep in mind that kernel pthreads
come with 1k stack by default. Increase it if you need more.

After pushing the array into global scope (and with the FPU fix applied)
your test works fine here over trunk.

Jan


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 250 bytes --]

      parent reply	other threads:[~2006-09-20 10:27 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <450B2BE1.1050105@domain.hid>
2006-09-16  4:38 ` Fw: [Fwd: Re: [Xenomai-help] invalid use of FPU in Xenomai context] Jeff Webb
2006-09-18 20:40   ` [Xenomai-help] invalid use of FPU in Xenomai context Jeff Webb
2006-09-18 21:23     ` Philippe Gerum
2006-10-25 20:00       ` Jeff Webb
2006-10-25 20:24         ` Jan Kiszka
2006-10-25 20:43           ` Jeff Webb
2006-10-25 23:37           ` Jeff Webb
2006-10-27 16:30             ` Jeff Webb
2006-09-20 10:27   ` Jan Kiszka [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=451117A1.50500@domain.hid \
    --to=jan.kiszka@domain.hid \
    --cc=jeff.webb@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.