Skip to contentSkip to conversation

Patch to fix glibc 2.1.2 so that new semaphore functions work in high signal env.

PATCH Kevin Hendricks 1 participant 1 message Oct 8, 1999 3 messages not in the archive

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): [email protected]

A message that is not in the archive (sent off-list or not yet received): v04011700b41f63005778@[204.210.50.90]

A message that is not in the archive (sent off-list or not yet received): v04011701b422cbe2027e@[204.210.50.90]

#3 lore raw

Hi,

I had to make the following patch to get glibc 2.1.2 new semaphores to work in high signal environments. For some reason calls to sem_post made by the pthread manager thread were *NOT* resolving to the __new_sem_post but instead to somewhere else (__old_sem_post or to kernel sem_post ????).

I don't know why (the correct fix might be somewhere else) but this does the trick.

The pthread manager only does the sem_post calls when the original thread was in a signal handler.

I am not sure this will help others, but it does wonders for the JDK!!!

Thanks,

Kevin

manager.c renamed from manager.c.prev +1 -1
@@ -156,7 +156,7 @@
         }
         break;
       case REQ_POST:
-        sem_post(request.req_args.post);
+        __new_sem_post(request.req_args.post);
         break;
       case REQ_DEBUG:
 	/* Make gdb aware of new thread and gdb will restart the