search for: pthread_kil

...c/asterisk/loader.c:282: undefined reference to `dlclose' loader.o: In function `ast_update_module_list': /usr/src/asterisk/loader.c:434: undefined reference to `pthread_mutex_trylock' channel.o: In function `ast_queue_frame': /usr/src/asterisk/channel.c:396: undefined reference to `pthread_kill' channel.o: In function `ast_do_masquerade': /usr/src/asterisk/channel.c:2112: undefined reference to `pthread_kill' channel.o: In function `tonepair_generator': /usr/src/asterisk/channel.c:2418: undefined reference to `sin' /usr/src/asterisk/channel.c:2418: undefined reference...

...;> Hi, >> >> I tried that out, I got a new error about pthreads in my config.log. > > It finds the header file now which is good, but it still fails to > find the libpthread.dll file, which is what LDFLAGS should have > addressed > > configure:15417: checking for pthread_kill in -lpthread > configure:15442: gcc -o conftest.exe -I/c/msys64/mingw64/x86_64-w64-mingw32/include/ -L/c/msys64/mingw64/x86_64-w64-mingw32/lib/:/c/msys64/mingw64/bin/ conftest.c -lpthread >&5 > c:/mingw/bin/../lib/gcc/mingw32/8.2.0/../../../../mingw32/bin/ld.exe: cannot find -lpthr...

Hi, I tried that out, I got a new error about pthreads in my config.log. Could you take another look. Thanks again, Reza > On Aug 20, 2019, at 12:36 PM, Daniel P. Berrangé <berrange@redhat.com> wrote: > > On Tue, Aug 20, 2019 at 12:29:15PM -0400, reza shahriari wrote: >> Hi, >> >> I have attached my compressed config file. >> >> Thanks,

https://bugzilla.mindrot.org/show_bug.cgi?id=3522 Bug ID: 3522 Summary: Crash with "free(): double free detected" with old clients Product: Portable OpenSSH Version: 9.1p1 Hardware: amd64 OS: Linux Status: NEW Severity: minor Priority: P5 Component: sshd

...release. That's failing. The error thrown is: java(78745,0x70000241e000) malloc: *** error for object 0x7fd5df561390: pointer being freed was not allocated *** set a breakpoint in malloc_error_break to debug Frames from core dump: frame #0: 0x00007fff5b274b66 libsystem_kernel.dylib`__pthread_kill + 10 frame #1: 0x00007fff5b43f080 libsystem_pthread.dylib`pthread_kill + 333 frame #2: 0x00007fff5b1d01ae libsystem_c.dylib`abort + 127 frame #3: 0x00007fff5b2ce8a6 libsystem_malloc.dylib`free + 521 frame #4: 0x00000001127f43a7 frame #5: 0x00000001127e3ffd frame #6: 0...

...r pipe-to-self trick), or interrupt the polling with EINTR due to delivery of a signal. So, I played with the latter approach by running the reader thread with SIGUSR1 blocked except during the poll, where other threads change their kick action from writing into the pipe-to-self to instead calling pthread_kill() to force EINTR. Unfortunately, using only poll() for this is racy; to fix the race, we either have to resort to POSIX pselect() (which is horribly klunky and does not scale well to large fd values if we have lots of parallel clients) or use the non-POSIX ppoll() (these days, BSD and Linux syste...

...1:03:40PM -0400, reza shahriari wrote: > Hi, > > I tried that out, I got a new error about pthreads in my config.log. It finds the header file now which is good, but it still fails to find the libpthread.dll file, which is what LDFLAGS should have addressed configure:15417: checking for pthread_kill in -lpthread configure:15442: gcc -o conftest.exe -I/c/msys64/mingw64/x86_64-w64-mingw32/include/ -L/c/msys64/mingw64/x86_64-w64-mingw32/lib/:/c/msys64/mingw64/bin/ conftest.c -lpthread >&5 c:/mingw/bin/../lib/gcc/mingw32/8.2.0/../../../../mingw32/bin/ld.exe: cannot find -lpthread | char...

I was just trying astman with the latest svn trunk from Dec 31. It connects, but if I attempt to make a call, asterisk segfaults, but in pthread_kill in /lib/tls/libpthread.so not in the asterisk code. Is this something others have seen? This is with glibc-2.3.4-2 I just upgraded to 2.3.6 (the lastest for Fedora core 3) and it's the same. Not much of a traceback, it's happening here: static struct eventqent *unref_event(struct e...

...:47:17 imap(pid 50490 user submit): Panic: file imap-client.c: line 643 (client_command_free): assertion failed: (client->output_cmd_lock == NULL) The line number doesn't match dovecot-2.2.1 due to Apple's unrelated modifications. 0 libsystem_kernel.dylib 0x00007fff8a9f7d4a __pthread_kill + 10 1 libsystem_pthread.dylib 0x00007fff8f728705 pthread_kill + 92 2 libsystem_c.dylib 0x00007fff8f48b17b abort + 125 3 libdovecot.0.dylib 0x000000010db8d2bb default_fatal_finish + 68 4 libdovecot.0.dylib 0x000000010db8df66 i_internal_error_hand...

...orary(Node); 401 } 402 (lldb) print Node (llvm::MDNode *) $3 = 0x00000001180b74c0 (lldb) call Node->dump() !{i32 786468} (lldb) call V->dump() !{} (lldb) Here’s the first part of the backtrace: (lldb) bt * thread #1: tid = 0x4ec96f, 0x00007fff93137866 libsystem_kernel.dylib`__pthread_kill + 10, queue = 'com.apple.main-thread', stop reason = signal SIGABRT frame #0: 0x00007fff93137866 libsystem_kernel.dylib`__pthread_kill + 10 frame #1: 0x00007fff8cd8035c libsystem_pthread.dylib`pthread_kill + 92 frame #2: 0x0000000103ca78ab clasp_boehm_d`raise(sig=6) + 27 at Sig...

...malloc: *** error for object 0x7fd5df561390: > > pointer being freed was not allocated > > > > *** set a breakpoint in malloc_error_break to debug > > > > > > Frames from core dump: > > > > frame #0: 0x00007fff5b274b66 libsystem_kernel.dylib`__pthread_kill + 10 > > > > frame #1: 0x00007fff5b43f080 libsystem_pthread.dylib`pthread_kill + 333 > > > > frame #2: 0x00007fff5b1d01ae libsystem_c.dylib`abort + 127 > > > > frame #3: 0x00007fff5b2ce8a6 libsystem_malloc.dylib`free + 521 > > > >...

...(ins Int32Regs:$a), 1247 "test $dst0, $dst1, $a;", 1248 [(set Int32Regs:$dst0, Int32Regs:$dst1, (TestNode Int32Regs:$a))]>; ... TableGen crashes with the following stack trace: #0 0x00007fff8f372212 in __pthread_kill () #1 0x00007fff8dc0eaf4 in pthread_kill () #2 0x00000001003a978b in raise (sig=6) at Signals.inc:345 #3 0x00000001003a9842 in abort () at Signals.inc:362 #4 0x00000001003a9821 in __assert_rtn (func=0x1003d0d14 "operator[]", file=0x1003b169e "/Users/jholewinski/projects/llvm/src...

...wd } -------------------------------------------------------------------------------- gdb backtrace via coredumpctl debug PID: Core was generated by `dovecot/imap'. Program terminated with signal SIGABRT, Aborted. --Type <RET> for more, q to quit, c to continue without paging-- #0 __pthread_kill_implementation (threadid=<optimized out>, signo=signo at entry=6, no_tid=no_tid at entry=0) at pthread_kill.c:44 44 return INTERNAL_SYSCALL_ERROR_P (ret) ? INTERNAL_SYSCALL_ERRNO (ret) : 0; (gdb) bt...

...t32Regs:$a), > 1247 "test $dst0, $dst1, $a;", > 1248 [(set Int32Regs:$dst0, Int32Regs:$dst1, > (TestNode Int32Regs:$a))]>; > > ... TableGen crashes with the following stack trace: > > #0 0x00007fff8f372212 in __pthread_kill () > #1 0x00007fff8dc0eaf4 in pthread_kill () > #2 0x00000001003a978b in raise (sig=6) at Signals.inc:345 > #3 0x00000001003a9842 in abort () at Signals.inc:362 > #4 0x00000001003a9821 in __assert_rtn (func=0x1003d0d14 "operator[]", > file=0x1003b169e > "/Users...

...-system-libs --libs all`-o dump* *$ ./dump* But I am getting a segmentation fault as given below. What may be causing this? I am on llvm-6.0 rc2. > * thread #1, queue = 'com.apple.main-thread', stop reason = signal SIGABRT > * frame #0: 0x00007fff71902e3e libsystem_kernel.dylib`__pthread_kill + 10 > frame #1: 0x00007fff71a41150 libsystem_pthread.dylib`pthread_kill + 333 > frame #2: 0x00007fff7185f312 libsystem_c.dylib`abort + 127 > frame #3: 0x00007fff71827368 libsystem_c.dylib`__assert_rtn + 320 > frame #4: 0x0000000100477eb9 dump`llvm::isa_impl_cl<llvm:...

...ng freed was not allocated > > > > > > > > *** set a breakpoint in malloc_error_break to debug > > > > > > > > > > > > Frames from core dump: > > > > > > > > frame #0: 0x00007fff5b274b66 libsystem_kernel.dylib`__pthread_kill > > + 10 > > > > > > > > frame #1: 0x00007fff5b43f080 libsystem_pthread.dylib`pthread_kill > > + 333 > > > > > > > > frame #2: 0x00007fff5b1d01ae libsystem_c.dylib`abort + 127 > > > > > > > > frame #3:...

...Int32Regs:$a), > 1247 "test $dst0, $dst1, $a;", > 1248 [(set Int32Regs:$dst0, Int32Regs:$dst1, (TestNode Int32Regs:$a))]>; > > ... TableGen crashes with the following stack trace: > > #0 0x00007fff8f372212 in __pthread_kill () > #1 0x00007fff8dc0eaf4 in pthread_kill () > #2 0x00000001003a978b in raise (sig=6) at Signals.inc:345 > #3 0x00000001003a9842 in abort () at Signals.inc:362 > #4 0x00000001003a9821 in __assert_rtn (func=0x1003d0d14 "operator[]", file=0x1003b169e "/Users/jholewins...

...anks everyone for all the comments. I think maybe I wasn't clear that I *only* care about atomicity w.r.t. a signal handler interruption in the same thread, *not* across threads. Therefore, many of the problems of cross-CPU atomicity are not relevant. The signal handler gets invoked via pthread_kill, and is thus necessarily running in the same thread as the code being interrupted. The memory in question can be considered thread-local here, so I'm not worried about other threads touching it at all. I also realize I had (at least :) one error in my original email: of course, the at...

...1247 "test $dst0, $dst1, $a;", >> 1248 [(set Int32Regs:$dst0, Int32Regs:$dst1, (TestNode Int32Regs:$a))]>; >> >> ... TableGen crashes with the following stack trace: >> >> #0 0x00007fff8f372212 in __pthread_kill () >> #1 0x00007fff8dc0eaf4 in pthread_kill () >> #2 0x00000001003a978b in raise (sig=6) at Signals.inc:345 >> #3 0x00000001003a9842 in abort () at Signals.inc:362 >> #4 0x00000001003a9821 in __assert_rtn (func=0x1003d0d14 "operator[]", file=0x1003b169e "...

...e for all the comments. I think maybe I wasn't clear that > I *only* care about atomicity w.r.t. a signal handler interruption in the > same thread, *not* across threads. Therefore, many of the problems of > cross-CPU atomicity are not relevant. The signal handler gets invoked via > pthread_kill, and is thus necessarily running in the same thread as the code > being interrupted. The memory in question can be considered thread-local > here, so I'm not worried about other threads touching it at all. Ok, this helps make sense, but it still is confusing to phrase this as "sing...