[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Condor-devel] Master Bombs on Iherited Sockets on Collector Startup
- Date: Thu, 2 Jun 2011 11:27:46 -0500
- From: Brian Bockelman <bbockelm@xxxxxxxxxxx>
- Subject: Re: [Condor-devel] Master Bombs on Iherited Sockets on Collector Startup
Hi Alan,
From the GDB issue on your ticket: I've been fighting with getting GDB functioning for awhile. It seems to get better with:
USE_CLONE_TO_CREATE_PROCESSES = false
Best I can figure, GDB is assuming certain things about threads after a clone that pthreads does but Condor's cloning doesn't. Without the above, GDB reliably pukes each time.
Brian
On Jun 2, 2011, at 11:08 AM, Alan De Smet wrote:
> Matthew Farrellee <matt@xxxxxxxxxx> wrote:
>> Local for me - CONDOR_INHERIT: "20790 <127.0.0.1:47811> 0
>> 13*6*0*0*0*0***1*<127.0.0.1:0>*0*0* 14*2*0*0*0*0***0*<127.0.0.1:0>* 0"
>>
>> In the log - CONDOR_INHERIT: "5137 0 9*6*0*0*0*0***1**0*0*
>> 10*2*0*0*0*0***0** 0"
>>
>> Possibly the serialization was broken?
>
> Indeed. Symptoms appear elsewhere. I've been through the code
> path in question with a fine tooth comb, and I can confidently
> say that the behavior in question can't happen. Thus, the
> flawed output I'm seeing in my own logs must be hallucinations.
> :-/
>
> Continuing investigation.
>
> https://condor-wiki.cs.wisc.edu/index.cgi/tktview?tn=2205,21
>
> --
> Alan De Smet Condor Project Research
> adesmet@xxxxxxxxxxx http://www.cs.wisc.edu/condor/
> _______________________________________________
> Condor-devel mailing list
> Condor-devel@xxxxxxxxxxx
> https://lists.cs.wisc.edu/mailman/listinfo/condor-devel