similar to: Problem with psignal.c for Windows builds

Continuing with problems that I've uncovered while getting pqR to work on Windows... The file src/ghuwin32/psignal.c (used only in Windows builds) fails to use the sigset_t type in all places where it should, using "int" some places instead. Here is a diff of the needed corrections: @@ -253,7 +253,7 @@ sighandler_t signal(int signal_Number, sighandler_t signal_Handler) int

Commit-ID: 5c65fe97c9c00feb5ed10598dcd51ef7399be7ff Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=5c65fe97c9c00feb5ed10598dcd51ef7399be7ff Author: Herbert Xu <herbert at gondor.apana.org.au> AuthorDate: Wed, 21 Nov 2018 11:45:04 +0800 Committer: Ben Hutchings <ben at decadent.org.uk> CommitDate: Sat, 28 Mar 2020 21:42:55 +0000 [klibc] dash: system: Disable

Hi , I needed to apply this patch to get the GCC frontend building on an FC5 x86 box . [ramana at venglathur gcc]$ svn diff Index: libiberty/strsignal.c =================================================================== --- libiberty/strsignal.c (revision 254) +++ libiberty/strsignal.c (working copy) @@ -557,8 +557,8 @@ void psignal (signo, message) - unsigned signo; -

On Jan 24, 2007, at 4:14 AM, Ramana Radhakrishnan wrote: > Hi , > > I needed to apply this patch to get the GCC frontend building on an > FC5 > x86 box . I am curious, what kind of failure are you seeing ? Thanks, - Devang

Devang, On Wed, 2007-01-24 at 10:28 -0800, Devang Patel wrote: > On Jan 24, 2007, at 4:14 AM, Ramana Radhakrishnan wrote: > > > Hi , > > > > I needed to apply this patch to get the GCC frontend building on an > > FC5 > > x86 box . > > I am curious, what kind of failure are you seeing ? I should have mentioned in the email : Here's my earlier post

Hi I hope this isn't a FAQ, but i've scoured and found nothing. When compiling samba 1.9.18p8 with AFS 3.4a on solaris 2.6, when I go to link the binary (smbd) with the stock makefiles, i get: Undefined first referenced symbol in file sigvec /usr/afsws/lib/liblwp.a(iomgr.o) sigsetmask

So, we just found some ugly behaviour of OpenSSH on Solaris. Sometimes, it seems, sshd gets started with SIGCHLD blocked, this, apparently, being the setting of sshd's parent (a shell no doubt); signal blocking is inherited across exec*(). I don't know exactly which shell, or what really is at fault, but it happens. The problem is that the code in collect_children() first blocks SIGCHLD

klibc fails to build on ia64 because it has neither fork nor the ppoll syscalls. This patch marks the former in SYSCALLS.def, and puts a guard wrapper around the ppoll definition in ppoll.c Should these calls return ENOSYS rather than simply not existing on some systems? If yes, please apply this and I'll follow up with a patch shortly that does ENOSYS for this and pselect at least.

Well, 4 days after previous upgrade i cvs'ed RELENG_4 from local cvs tree (updated hourly), made buildworld buildkernel installkernel, rebooted into single user, made installworld and mergemaster. Mergemaster updated newsyslog.conf, syslogd.conf, ok, rebooted... Wow... All scripts from /usr/local/etc/rc.d refused to load. And the system is in "Amnesiac" mode Attempt to run

On Sun, May 21, 2023 at 09:51:24PM -0500, Mike Christie wrote: > When switching from kthreads to vhost_tasks two bugs were added: > 1. The vhost worker tasks's now show up as processes so scripts doing ps > or ps a would not incorrectly detect the vhost task as another process. > 2. kthreads disabled freeze by setting PF_NOFREEZE, but vhost tasks's > didn't disable or

SIGSUSPEND(2) Linux Programmer's Manual SIGSUSPEND(2) NAME sigsuspend - wait for a signal SYNOPSIS #include <signal.h> int sigsuspend(const sigset_t *mask); ? and ? SIGSUSPEND(2) BSD Programmer's Manual SIGSUSPEND(2) NAME sigsuspend - atomically release blocked signals and wait for interrupt SYNOPSIS

Op 20-10-2017 om 4:23 schreef Reuben Farrelly: > On 18/10/2017 11:40 PM, Timo Sirainen wrote: >> On 18 Oct 2017, at 6.34, Reuben Farrelly <reuben-dovecot at reub.net> >> wrote: >>> >>> I haven't been tracking dovecot-2.3 until now, but I've just given >>> it a quick run, and there are a few things that may need some >>> attention.

Now, the conversion hangs on the first disk at 54,03/100%, here is the gdb result : (gdb) t a a bt Thread 2 (Thread 0x7f0f3cea9700 (LWP 9583)): #0 sem_timedwait () at ../nptl/sysdeps/unix/sysv/linux/x86_64/sem_timedwait.S:101 #1 0x00007f0f45b765e7 in qemu_sem_timedwait () #2 0x00007f0f45b0750c in worker_thread () #3 0x00007f0f4203bdf3 in start_thread (arg=0x7f0f3cea9700) at

Hello, We would like to continue a Perl AGI after a Dial() it has done completes following caller hangup. We would like to do this in the same AGI, and not using a new AGI from the 'h' extension. It works fine when the called party hangs up and the 'g' option is used, but not for caller hangup. Is this possible? If not a confirmation that this is the case would be very helpful.

Killall does nothing the process is still alive... If I do kill -9, do I get a core dump ? Each time I got this hang, I find only umount -f /tmp/xxxx to force qemu-img to stop. Alain -----Message d'origine----- De : Richard W.M. Jones [mailto:rjones@redhat.com] Envoyé : mercredi 15 octobre 2014 14:41 À : VONDRA Alain Cc : libguestfs@redhat.com Objet : Re: [Libguestfs] Virt-v2v conversion

https://bugs.freedesktop.org/show_bug.cgi?id=93197 Bug ID: 93197 Summary: Warsow 2.0 crashes in nouveau_fence_trigger_work Product: Mesa Version: git Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: major Priority: medium Component: Drivers/DRI/nouveau Assignee:

comments? alternatives: sigsetjmp(ugly) and pselect(not portable, available) drawback: additional filedescriptors. Index: serverloop.c =================================================================== RCS file: /home/markus/cvs/ssh/serverloop.c,v retrieving revision 1.82 diff -u -r1.82 serverloop.c --- serverloop.c 10 Oct 2001 22:18:47 -0000 1.82 +++ serverloop.c 11 Oct 2001 18:06:33 -0000 @@

On Wed, Oct 15, 2014 at 12:23:17PM +0000, VONDRA Alain wrote: > Now, the conversion hangs on the first disk at 54,03/100%, here is the gdb result : OK I just talked to Paolo about this, and it's fairly serious. Can you get a core dump from this? You will need to set up the ulimit etc as outlined in the previous email: https://www.redhat.com/archives/libguestfs/2014-October/msg00102.html

Sure.? Here you go: Oct 13 23:45:01 thunderstorm.reub.net dovecot: imap-login: Login: user=<reuben>, auth-method=PLAIN, remote=2001:44b8:x:x, local=2001:44b8:31d4:x:x, TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits) Oct 13 23:45:03 thunderstorm.reub.net dovecot: doveadm: Error: ==16947== Syscall param epoll_pwait(sigmask) points to unaddressable byte(s) Oct 13 23:45:03

On 18/10/2017 11:40 PM, Timo Sirainen wrote: > On 18 Oct 2017, at 6.34, Reuben Farrelly <reuben-dovecot at reub.net> wrote: >> >> I haven't been tracking dovecot-2.3 until now, but I've just given it a quick run, and there are a few things that may need some attention. >> >> /usr/include/features.h:376:4: warning: #warning _FORTIFY_SOURCE requires compiling