[Bug nptl/3610] New: coredump on pthread_mutex_lock()

classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|

[Bug nptl/3610] New: coredump on pthread_mutex_lock()

yangyibiao at hust dot edu.cn
There is a chance that glibc/nptl is not the cause of this, but I cannot say
for sure.
Note that this is glibc 2.5, not 2.4 as stated in the version field.
Thanks

Example 1:
#3  0x000073fc in ?? ()
#4  0xb797181b in *__GI_raise (sig=6)
at ../nptl/sysdeps/unix/sysv/linux/raise.c:67
#5  0xb79731e8 in *__GI_abort () at abort.c:88
#6  0xb796af2c in *__GI___assert_fail (assertion=0xb7a86b04 "new_prio == -1 ||
(new_prio >= __sched_fifo_min_prio && new_prio <= __sched_fifo_max_prio)",
    file=0xb7a86ae0 "tpp.c", line=63,
function=0xb7a86ae6 "__pthread_tpp_change_priority") at assert.c:78
#7  0xb7a84db2 in __pthread_tpp_change_priority (previous_prio=-1,
new_prio=3825) at tpp.c:61
#8  0xb7a7db5b in __pthread_mutex_lock (mutex=0x81162fc) at
pthread_mutex_lock.c:379


Example 2:
#4  0xb799e577 in *__GI_raise (sig=6)
at ../nptl/sysdeps/unix/sysv/linux/raise.c:67
#5  0xb79a00ea in *__GI_abort () at abort.c:88
#6  0xb799782c in *__GI___assert_fail (assertion=0x6 <Address 0x6 out of
bounds>, file=0x6 <Address 0x6 out of bounds>, line=6,
    function=0xb7abbf78 "__pthread_tpp_change_priority") at assert.c:78
#7  0xb7ab9ddf in __pthread_tpp_change_priority (previous_prio=-1,
new_prio=1527) at tpp.c:61
#8  0xb7ab27b5 in __pthread_mutex_lock (mutex=0x908db1c) at
pthread_mutex_lock.c:379

Hardware: dual xeon x64 with hyperthreads
Kernel 2.6.18.1 and 2.6.18.2

--
           Summary: coredump on pthread_mutex_lock()
           Product: glibc
           Version: 2.4
            Status: NEW
          Severity: normal
          Priority: P2
         Component: nptl
        AssignedTo: drepper at redhat dot com
        ReportedBy: sources dot redhat dot com at hovland dot cx
                CC: glibc-bugs at sources dot redhat dot com
 GCC build triplet: i686-j-linux
  GCC host triplet: i686-j-linux
GCC target triplet: i686-j-linux


http://sourceware.org/bugzilla/show_bug.cgi?id=3610

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
Reply | Threaded
Open this post in threaded view
|

[Bug nptl/3610] coredump on pthread_mutex_lock()

yangyibiao at hust dot edu.cn

------- Additional Comments From sources dot redhat dot com at hovland dot cx  2006-11-29 12:28 -------
The mutex was created with the PTHREAD_MUTEX_RECURSIVE attribute.

--


http://sourceware.org/bugzilla/show_bug.cgi?id=3610

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
Reply | Threaded
Open this post in threaded view
|

[Bug nptl/3610] coredump on pthread_mutex_lock()

yangyibiao at hust dot edu.cn
In reply to this post by yangyibiao at hust dot edu.cn

------- Additional Comments From jakub at redhat dot com  2006-11-29 12:35 -------
Do you have a testcase?

--
           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |WAITING


http://sourceware.org/bugzilla/show_bug.cgi?id=3610

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
Reply | Threaded
Open this post in threaded view
|

[Bug nptl/3610] coredump on pthread_mutex_lock()

yangyibiao at hust dot edu.cn
In reply to this post by yangyibiao at hust dot edu.cn

------- Additional Comments From jakub at redhat dot com  2006-11-29 12:43 -------
Also, were there calls to pthread_mutexattr_setprotocol?
If not, this sounds like either uninitialized mutex or unitialized mutex
attribute.

--


http://sourceware.org/bugzilla/show_bug.cgi?id=3610

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
Reply | Threaded
Open this post in threaded view
|

[Bug nptl/3610] coredump on pthread_mutex_lock()

yangyibiao at hust dot edu.cn
In reply to this post by yangyibiao at hust dot edu.cn

------- Additional Comments From sources dot redhat dot com at hovland dot cx  2006-11-29 14:28 -------
pthread_mutexattr_init was not called, just *_settype. Case closed:) Thanks
for your help.

--
           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|WAITING                     |RESOLVED
         Resolution|                            |INVALID


http://sourceware.org/bugzilla/show_bug.cgi?id=3610

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.