[bug #24054] Segmentation fault in GSTest

[Fred Kiefer]

Follow-up Comment #9, bug #24054 (project gnustep):

I changed my printf statement and moved it to different places. This is what
I get now:

end thread pool cache 0x823ad04 current thread 0x823ace0 ended thread
0xb40004c0 count 1
push pool 0x823b330 thread 0x823ace0 count 2
pop pool 0x823b330 thread 0x823ace0 count 2
push pool 0x8222ee8 thread 0x823ace0 count 2
pop pool 0x8222ee8 thread 0x823ace0 count 2
push pool 0x8342e90 thread 0x823ace0 count 2
pop pool 0x8342e90 thread 0x823ace0 count 2
free pool cache 0x823ad04 thread 0x823ace0 count 1
pop pool 0x82425b8 thread 0x823ace0 count 1
finished free pool cache 0x823ad04 thread 0x823ace0 count 0
empty pool 0x823b330 thread 0x823ace0

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0xb5920b90 (LWP 9299)]
0xb78b9734 in objc_msg_lookup () from /usr/lib/libobjc.so.2

Some thread finishes and from the endThread: method we try to clean up the
corresponding pool cache. But it looks like we clean up the pool cache of the
current thread and of course things go horribly wrong after that. At least
this is how I interpret the printed results at the moment. I will try to
change the code and see if it improves things.


    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?24054>

_______________________________________________
  Nachricht geschickt von/durch Savannah
  http://savannah.gnu.org/