> On 04/29/2012 06:08 PM, David C. Rankin wrote:
>>   Also, why do you encouragingly say "I really, really [hope] this is
>> NOT the
>> cause..."? Just curious. Here is the backtrace with the funky line right
>> before bt:
>>
>
> Geez! Now I see why you say that.... I just did diffs of different points
> in the
> tdebase code:
>
> -rw-r--r-- 1 david david 142792 Apr 29 18:48 0329-0410_tdebase.diff
> -rw-r--r-- 1 david david  97205 Apr 29 18:51 0410-0420_tdebase.diff
> -rw-r--r-- 1 david david  76893 Apr 29 18:52 0420-0425_tdebase.diff
>
> That's almost 310k in diffs between 3/29 and 4/25. Wow.. That's the point
> that
> might make it a bit difficult to find...
>
> Oh well, How do you eat a whale ---> one bite at a time. Let's start
> eating...
>

I'd look at tqt3, arts, tdelibs, and *maybe* tdebase, but honestly I think
the problem is in tdelibs
(http://git.trinitydesktop.org/cgit/tdelibs/log/).  Easiest way to debug
this is:
1.) Check out and rebuild/reinstall tqt3, arts, tdelibs, and tdebase from
the last known working date.
2.) Update, rebuild, and reinstall each module in turn, checking for the
failure after each module has been reinstalled with the latest sources. 
3.) Once the module is known (e.g. tdelibs or tdebase causes the problem),
bisect the commits between the known working date and the latest HEAD.

Tedious, but you should get the faulty commit fastest this way.

Tim