trinity-devel@lists.pearsoncomputing.net

Message: previous - next
Month: May 2012

Re: [trinity-devel] TIME Frame 3/29 -> 4/10 kwrite crash introduced

From: "David C. Rankin" <drankinatty@...>
Date: Tue, 01 May 2012 08:56:29 -0500
On 04/30/2012 11:25 PM, Darrell Anderson wrote:
> I have a lot of things outside the project suddenly pulling at me, which doesn't help and certainly added to today's stress. The ebb and flow of life. The best approach is to take care of those things. I don't expect to help for a few days but I'll keep tabs on the emails as best I can.
>

Yep, you and I both have pushed things to the side to focus on TDE and getting 
it ready for R14 in good shape. I have a bit of catch-up to play myself. Go 
get the other half of life back up to par and I'll continue picking away at 
this. I will have to pull a fresh 3/29 git tree down and then work forward to 
4/4. I can do so creating tarballs as I update to ensure I have a set for each 
day (if not each commit).

I share your frustration. R13 was just getting into good shape when gcc 4.5.2 
was released that caused similar problems. Not near the extent that 4.7 has, 
but frustrating nonetheless. We will find the issue somehow.

I'll go look for the clone command that will let me pull a fresh 3/29 tree. If 
you know the command, that would save me the time, but I suspect it is already 
in the wiki or man git will do it. (the submodules might be a trick)

Luckily, there are only a few gcc 4.7 patches needed to build through tdebase. 
We will just apply them as needed to debug. Back at it....

> I'm sure this won't be the last time we need to reset the sources for debugging purposes. If you get through this ordeal without losing your mind then perhaps a short wiki how-to would be nice. :-)

Amen...

Nothing like shooting at a moving target to hone your marksmanship skills...

-- 
David C. Rankin, J.D.,P.E.