> On 04/25/2012 01:26 PM, David C. Rankin wrote:
>> On 04/25/2012 12:59 PM, Timothy Pearson wrote:
>>> I would make absolutely certain that kwrite isn't in D state (via 'ps
>>> aux') or similar during the hang before filing a report.  TDE
>>> applications
>>> seem to be somewhat sensitive to swap and disk I/O in general in my
>>> experience.
>>>
>>> Other than that, the best thing you can do is use gdb to break into
>>> kwrite
>>> while it is hung and generate a backtrace.
>>>
>>> Tim
>>
>>   Not sure what D state is, but I can certainly test and see what is up.
>>
>> Before hang:
>>
>> david    12822  1.7  3.1 207448 23712 ?        S    13:21   0:00 kwrite
>> [tdeinit]
>>
>> After hang:
>>
>> david    12822  9.3  3.1 207912 23900 ?        R    13:21   0:07 kwrite
>> [tdeinit]
>>
>> david    12822 66.2  3.1 207912 23900 ?        R    13:21   2:32 kwrite
>> [tdeinit]
>>
>> and it just stays there.
>>
>>   Now, how do I "use gdb to break into kwrite"? Just a the command form
>> you want
>> like:
>>
>> gdb what :)
>>
>
> got it -- now what (rebuild and don't strip :)

Yep, that's correct.  Once you get to the gdb> prompt enter 'bt' and press
<return>.

Tim