[Bug 253318] lldb: aborted when debugging named
bugzilla-noreply at freebsd.org
bugzilla-noreply at freebsd.org
Sun Feb 7 16:33:37 UTC 2021
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=253318
--- Comment #1 from Dimitry Andric <dim at FreeBSD.org> ---
Any idea how to reproduce this? It appears that mutex::lock() just calls
pthread_mutex_lock() and it fails somehow:
00000000000b5380 <std::__1::mutex::lock()@@Base>:
b5380: 55 push %rbp
b5381: 48 89 e5 mov %rsp,%rbp
b5384: e8 67 e7 00 00 callq c3af0 <pthread_mutex_lock at plt>
b5389: 85 c0 test %eax,%eax
b538b: 75 02 jne b538f
<std::__1::mutex::lock()@@Base+0xf>
b538d: 5d pop %rbp
b538e: c3 retq
b538f: 48 8d 35 e8 a0 f8 ff lea -0x75f18(%rip),%rsi #
3f47e <typeinfo name for std::bad_any_cast@@Base-0x8df>
b5396: 89 c7 mov %eax,%edi
b5398: e8 d3 d2 00 00 callq c2670
<std::__1::__throw_system_error(int, char const*)@plt>
So in frame 5, can you print the value of 'ec' ? pthread_mutex_lock(3) says:
ERRORS
The pthread_mutex_lock() function will fail if:
[EINVAL] The value specified by mutex is invalid.
[EDEADLK] A deadlock would occur if the thread blocked waiting
for mutex.
[EOWNERDEAD] The argument mutex points to a robust mutex and the
process containing the previous owning thread
terminated while holding the mutex lock. The lock
was granted to the caller and it is up to the new
owner to make the state consistent.
[ENOTRECOVERABLE] The state protected by the mutex is not recoverable.
I wonder what the actual error is...
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the freebsd-bugs
mailing list