From: "Petr Cervenka" <grugh@domain.hid>
To: xenomai@xenomai.org
Subject: [Xenomai-help] Segmentation error by heavy dynamic RT_QUEUE usage
Date: Thu, 31 Jul 2008 18:14:08 +0200 [thread overview]
Message-ID: <200807311814.25994@domain.hid> (raw)
In-Reply-To: <48847272.3080605@domain.hid>
[-- Attachment #1: Type: text/plain, Size: 1457 bytes --]
Hello,
I wanted to make an small example to find the kernel panic (and I failed with it). But during my tests I found another possible error.
I made a small application (as netbeans c++ project) with two tasks:
1) server task with its RT_QUEUE waiting for a request.
2) client task which creates RT_QUEUES for response and sends requests to the server task
>From time to time I get an segmentation error.
It's always in the server task, when the server binds the clients queue, allocates a message buffer in it.
It seems when the server starts to work with this buffer, the client could already close the queue.
But this shouldn't be possible, because normally any attempt to close a queue binded by someone else ends with -EBUSY error.
The error needs some time to produce and 2 CPUs (cores). One for server and one for client.
My configuration(s):
Athlon XP 2600GHz X86_64
kernel 2.6.24 (and 2.6.25.11)
adeos 2.6.24 2.0-03 (and 2.0-07)
xenomai 2.4.1 and 2.4.4
I'm sending also examples of the execution script and proper input.txt file
both of them should be much longer (input.txt could be several MB)!!!!
In the attachement there is also disassemble of my executable
And finally, one of the segmentation error messages:
[ 2553.818731] QT_SERVER[5919]: segfault at 2aaaaac96800 rip 4022b5 rsp 4000fe00 error 6
But there are more types, but allways when working with the allocated send buffer.
I know, I'm annoying, but I can't help myself.... ;-)
Petr
[-- Attachment #2: queuetest.tar.bz2 --]
[-- Type: application/octet-stream, Size: 10090 bytes --]
[-- Attachment #3: runme --]
[-- Type: application/octet-stream, Size: 164 bytes --]
#!/bin/sh
../dist/Debug/GNU-Linux-x86/queuetest < input2.txt
../dist/Debug/GNU-Linux-x86/queuetest < input2.txt
../dist/Debug/GNU-Linux-x86/queuetest < input2.txt
[-- Attachment #4: input.txt --]
[-- Type: text/plain, Size: 156 bytes --]
send 490000
recv
echo 490000
sleep 100
send 490000
recv
echo 490000
sleep 100
send 490000
recv
echo 490000
sleep 100
send 490000
recv
echo 490000
sleep 100
[-- Attachment #5: queuetest.asm.tar.bz2 --]
[-- Type: application/octet-stream, Size: 52235 bytes --]
next prev parent reply other threads:[~2008-07-31 16:14 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-07 15:45 [Xenomai-help] Kernel panic: not syncing Petr Cervenka
2008-07-07 15:59 ` Philippe Gerum
2008-07-08 8:31 ` Petr Cervenka
2008-07-08 8:38 ` Jan Kiszka
2008-07-08 9:21 ` Gilles Chanteperdrix
2008-07-08 9:33 ` Jan Kiszka
2008-07-09 15:19 ` Petr Cervenka
2008-07-09 16:05 ` Philippe Gerum
2008-07-10 13:45 ` Petr Cervenka
2008-07-11 13:18 ` Petr Cervenka
2008-07-15 14:42 ` Petr Cervenka
2008-07-15 15:03 ` Jan Kiszka
2008-07-16 8:39 ` Petr Cervenka
2008-07-17 10:21 ` Jan Kiszka
2008-07-21 10:58 ` Petr Cervenka
2008-07-21 11:26 ` Jan Kiszka
2008-07-31 16:14 ` Petr Cervenka [this message]
2008-08-12 14:37 ` [Xenomai-help] Segmentation error by heavy dynamic RT_QUEUE usage Philippe Gerum
2008-08-13 11:01 ` [Xenomai-core] [PATCH] Fix stat overruns on 64-bit (was: [Xenomai-help] Kernel panic: not syncing) Jan Kiszka
2008-08-13 15:29 ` [Xenomai-core] [PATCH] Fix stat overruns on 64-bit Philippe Gerum
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=200807311814.25994@domain.hid \
--to=grugh@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.