From: K. Noel Belcourt (kbelco_at_[hidden])
Date: 2007-08-07 00:36:46
Hi Ion,
On Aug 6, 2007, at 10:08 PM, K. Noel Belcourt wrote:
> On Jul 25, 2007, at 12:39 AM, Ion Gaztañaga wrote:
>
>> K. Noel Belcourt wrote:
>>> The named_recursive test in boost.interprocess takes an excessive
>>> amount of time to run.
>> This sounds very strange. In my poor AMD this takes only a few
>> seconds
>> ;-) Can you give any additional hint on what can be happening?
>
> Well it doesn't exhibit this hang in any consistent fashion. Some
> nights it goes right though, other times it hangs (like tonight).
> I hooked named_recursive in gdb and dumped the call stack, it's
> attached. Anything else I can do to help debug this?
I should have mentioned that I ran ipcs, here's the output.
[~]$ ipcs -a
------ Shared Memory Segments --------
key shmid owner perms bytes nattch status
0x00000000 0 root 777 94208 0
0x00000000 65537 root 777 94208 1
------ Semaphore Arrays --------
key semid owner perms nsems
------ Message Queues --------
key msqid owner perms used-bytes messages
What kind of IPC object does this test create? Why is there no IPC
object in the kernel data structures? I don't believe there's
anything running on my system that would call ipcrm. There's two
copies of this test currently running on my system (gcc-3.4.3 and
gcc-4.0.1), would that matter?
19303 kbelco 25 0 14944 1380 1188 R 98.9 0.0 40:00.53
named_recursive
19328 kbelco 25 0 14988 1360 1176 R 98.9 0.0 34:25.73
named_recursive
-- Noel