From: Wolfgang Grandegger <wg@domain.hid>
To: niklaus.giger@domain.hid
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-core] Bug in taskSuspend for user mode vxworks
Date: Mon, 30 Oct 2006 08:31:53 +0100 [thread overview]
Message-ID: <4545AA69.9080609@domain.hid> (raw)
In-Reply-To: <200610292202.49810.niklaus.giger@domain.hid>
Niklaus Giger wrote:
> Am Samstag, 28. Oktober 2006 20:36 schrieb Wolfgang Grandegger:
>> Niklaus Giger wrote:
>>> Am Samstag, 28. Oktober 2006 14:54 schrieb Niklaus Giger:
>>>> Am Freitag, 27. Oktober 2006 18:38 schrieb Philippe Gerum:
>>>>> On Wed, 2006-10-25 at 23:46 +0200, Niklaus Giger wrote:
>>>>>> Hi
>> My impression from our last discussion was that your toolchain is
>> somehow broken as I was unable to reproduce your problems on (almost)
>> the same hardware
>>
>>> I think I really have to reactivate my old Walnut board to have common
>>> platform to test with Wolfgang Grandegger.
>> It would make more sense to use the ELDK4 for comparison. I don't think
>> it depends on the hardware.
> As I forced my son to run on his MacMini (Intel Core Duo) only Linux and no
> MacOsX (he discovered widelands and was quite happy), I had a platform where
> I could install the CD with ELDK 4.0, which I had laying around.
>
> After some setting up of my environment and tweaking my scripts to work with
> ELDK (e.g. adding --host=ppc CC=ppc_4xx-gcc to my xenomai/configure) I ended
--host=ppc-linux is already enough with CROSS_COMPILE=ppc_4xx- set.
> up with a nice environment and rootfs with much more precompiled programs
> than I had ever before. Debugging on the platform is now as good as on my
> PowerBook.
>
> My situation is now as follows:
> - ELDK 4.0 installed on Debian Etch MacMini
> - Using ELD 4.0 rootfs ppc_4xx
> - compiled the kernel uImage, modules, xenomai using ppc_4xx-gcc
> (but NOT adding any -mcpu=40x flag to the compiler)
>
> The trap 0 in /proc/xenomai/fault seems to count on each invocation of simple
> 0: 51 (Data or instruction access)
> gdb however no does not show anything abnormal, as it says now
>> This GDB was configured as "ppc-linux"...Using host libthread_db library
>> "/lib/tls/libthread_db.so.1".
>>
>> (gdb) run
>> Starting program: /bin/simple
>> [Thread debugging using libthread_db enabled]
>> [New Thread 805422032 (LWP 639)]
>> root_thread_init 4[New Thread 805455088 (LWP 642)]
>>
>> Program exited normally.
>> (gdb) quit
>
> Though I am still puzzled.
Could you please send me your Makefile or the compile command to make
"simple", then I would give it a try on my setup.
Wolfgang.
next prev parent reply other threads:[~2006-10-30 7:31 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-25 21:46 [Xenomai-core] Bug in taskSuspend for user mode vxworks Niklaus Giger
2006-10-27 16:38 ` Philippe Gerum
2006-10-28 12:54 ` Niklaus Giger
2006-10-28 17:16 ` Philippe Gerum
2006-10-28 17:40 ` Niklaus Giger
2006-10-28 18:00 ` Philippe Gerum
2006-10-28 18:28 ` Niklaus Giger
2006-10-28 18:03 ` Philippe Gerum
2006-10-28 18:36 ` Wolfgang Grandegger
2006-10-29 21:02 ` Niklaus Giger
2006-10-29 21:15 ` Philippe Gerum
2006-10-30 7:31 ` Wolfgang Grandegger [this message]
2006-10-30 7:09 ` Niklaus Giger
2006-10-31 8:14 ` Wolfgang Grandegger
2006-10-31 18:51 ` Niklaus Giger
2006-10-31 19:02 ` Wolfgang Grandegger
2006-10-31 19:17 ` Niklaus Giger
2006-10-31 20:07 ` Wolfgang Grandegger
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=4545AA69.9080609@domain.hid \
--to=wg@domain.hid \
--cc=niklaus.giger@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.