trinity-users@lists.pearsoncomputing.net

Message: previous - next
Month: January 2015

Re: [trinity-users] desktop crashing

From: dep <dep@...>
Date: Mon, 12 Jan 2015 22:00:49 -0500
said Michele Calgaro:

| Thanks for the info, no need to rerun the previous commands since the
| thread IDs are the same. Register r8 should contain the address of the
| locked mutex. Please try this in the open gdb console.
|
| (gdb) p *(pthread_mutex_t*)0xda51f8
| Expect something like:
|
|   __data = {
|     __lock = xxx,
|     __count = yyy,
|     __owner = thread_ID,
|   ....
|
| This should give the id of the thread which has locked the mutex. Please
| report back, then we take the next step.
| If gdb complains about pthread_mutex_t, please try this:
| print *((int*)(0xda51f8)+2)

(gdb) p *(pthread_mutex_t*)0xda51f8
No symbol table is loaded.  Use the "file" command.
(gdb) print *((int*)(0xda51f8)+2)
$1 = 30334
(gdb)

that's all i got.
-- 
dep

The shortest distance between you and playing great acoustic guitar:
the great new instructional DVDs from Marjorie Thompson, 
available at www.MarjorieThompson.com