search for: sigbuses

If your system does not support fallocate(2), we use ftruncate(2) to create an output file. fallocate(2) succeeds even if your disk have less space than the requested size, because it creates a sparse file. If you mmap such sparse file, you'll receive a SIGBUS when the disk actually becomes full. So, lld can die suddenly with SIGBUS when your disk becomes full, and currently we are not doing

On Mon, Oct 23, 2017 at 5:28 PM, Andrew Kelley <superjoe30 at gmail.com> wrote: > For Zig we use LLD as a library. So for us it would be better to avoid > global state such as SIGBUS (or any other signal handlers), instead > returning an error from the link function when linking fails. If lld can > encapsulate this signal handling and prevent the application using lld from >

On Mon, Oct 23, 2017 at 6:40 PM, Andrew Kelley <superjoe30 at gmail.com> wrote: > > > On Mon, Oct 23, 2017 at 9:30 PM, Rui Ueyama <ruiu at google.com> wrote: > >> On Mon, Oct 23, 2017 at 5:28 PM, Andrew Kelley <superjoe30 at gmail.com> >> wrote: >> >>> For Zig we use LLD as a library. So for us it would be better to avoid >>>

One of my servers has recently started giving an error every time I run "aide --check". I ran it manually twice today with the same results. The second time, I added the -V flag, but that didn't give me anything useful. The system is currently running CentOS 5.3. Nothing on the system has changed recently (that I am aware of). The Aide database hasn't been updated in a few

Somemore information regarding the smbstatus error. The sigbus error is occuring where I noted below. I now have data values to go along with the location. The SIGBUS generating bit is "entry_scanner_p->e.pid" which looks to be in an unaccessable area of memory. Looking back through the code, I find a couple of bizarities. For example file_scanner_p->num_share_mode_entries

But that would disable mmap IO on systems that don't support fallocate. I'm not sure if OpenBSD people are for example happy about that. On Mon, Oct 30, 2017 at 2:03 PM, Rafael Avila de Espindola < rafael.espindola at gmail.com> wrote: > Rui Ueyama via llvm-dev <llvm-dev at lists.llvm.org> writes: > > > If your system does not support fallocate(2), we use

Hi Folks, I'm trying to run samba on Solaris 9. It works OK when I don't compile in kerberos and ldap, but when with those two compiled in, smbd seems to freeze (nmbd and winbindd are OK). After a bit of investigation I notice something strange in truss: ... /1@1: -> libldap-2.3:ldap_free_urldesc(0x30dfe8, 0x32e048, 0x32dfb8, 0x3 /1@1: ->

On Mon, Oct 23, 2017 at 3:40 PM, Brian Cain <brian.cain at gmail.com> wrote: > > > On Mon, Oct 23, 2017 at 5:21 PM, Rui Ueyama via llvm-dev < > llvm-dev at lists.llvm.org> wrote: > >> If your system does not support fallocate(2), we use ftruncate(2) to >> create an output file. fallocate(2) succeeds even if your disk have less >> space than the

-------- Original Message -------- Subject: smbstatus getting a SIGBUS error Date: Thu, 08 Jun 2000 13:52:13 +0700 From: Arnold Troeger <stssart@bkk.unocal.com> To: samba-bugs@samba.org CC: arnold.troeger@bkk.unocal.com I'm running Samba 2.0.7 and have been having a few problems with it. Just to keep things focused, I'll stick with smbstatus as this one has been the longest lasting

Hi Folks, I'm trying to run samba on Solaris 9. It works OK when I don't compile in kerberos and ldap, but when with those two compiled in, smbd seems to freeze (nmbd and winbindd are OK). After a bit of investigation I notice something strange in truss: ... /1@1: -> libldap-2.3:ldap_free_urldesc(0x30dfe8, 0x32e048, 0x32dfb8, 0x3 /1@1: ->

Hi there, I run tinc with not ConnectTo, (and it can't tcp-connect to the relevant other tincd, because that tincd is behind a firewall --> that tincd usualy connects to my tincd). If I start that tincd alone (not connected at all) and do a ping some_other_ip, it gets a SIGBUS in route.c:207 in the function route_ipv4_unreachable at the line: hdr->ip_v = 4; This seems to be an

...mmand executed *POOF*. The daemon is getting a SIGBUS trying to handle the UMASK from /etc/default/login with sscanf(3C); It just so happens that I'm using gcc-3.3.1, and I can't say this is definitely an OS or libC or compiler issue. However, the 32 bit binary works, and the 64 bit binary SIGBUSes. Here is a demo that will work whether you are YASSP/JASS hardenened or whatever (because the umask is hard-coded instead of read from /etc/default/login). ---cut--- #include <stdio.h> #include <sys/types.h> #include <sys/stat.h> int main (){ char var[4] = "777\0"; m...

Any idea on what's causing this? Description: imap process crashed with SIGBUS. Versions: OS: Solaris 8, 9 Dovecot: 1.0-test57 Gcc: 3.2 Configure options: env CC=gcc CFLAGS="-O -g" ./configure \ --prefix=/var/dovecot \ --disable-ipv6 \ --with-ssl=openssl \ --with-ssldir=/etc/ssl \ --with-passwd-file \ --without-bsdauth \ --without-checkpassword \

Please keep responses on list. Can you please run valgrind on this, as it appears to be some sort of memory corruption issue. Aki > On April 7, 2017 at 5:37 AM Hongying Liu <hongyliu at redhat.com> wrote: > > > Thanks for your response. > > (gdb) p cache > $1 = (struct mail_cache *) 0x7fc4a811a320 > (gdb) p cache->hdr > $2 = (const struct mail_cache_header

Sorry for late response. This issue occurs ran randomly. So I don't know how to run valgrind command. 2017-04-10 17:14 GMT+08:00 Hongying Liu <hongyliu at redhat.com>: > Sorry for late response. > > This issue occurs ran randomly. So I don't know how to run valgrind > command. > > I upload the coredump. > > The version of dovecot is

I built OpenSSH as a 64-bit binary on Solaris 9, using gcc 3.3.2, OpenSSL 0.9.7c and zlib 1.2.1. sshd starts up normally, and will begin the login session, however, some time after it reads /etc/default/login, it faults and kills the connection. There are no error messages logged to syslog (with LogLevel set to DEBUG) or with the -ddd option. Here's a truss of the failure: 8132:

Does FreeBSD have fallocate(2) or equivalent? On Mon, Oct 30, 2017 at 4:32 PM, Ed Maste <emaste at freebsd.org> wrote: > On 23 October 2017 at 18:49, Rui Ueyama via llvm-dev > <llvm-dev at lists.llvm.org> wrote: > >> > >> BTW, posix_fallocate() might provide better portability and decrease the > >> likelihood of falling back on ftruncate(). > >

http://bugs.freedesktop.org/show_bug.cgi?id=11492 riccardo at datahost.it changed: What |Removed |Added ---------------------------------------------------------------------------- QAContact|eric at anholt.net |swfdec at lists.freedesktop.org Status|NEEDINFO |NEW AssignedTo|eric at anholt.net

Hi sbr-services, Could you give me some idea? ### abrt reported the error as below. [root at cupop4 log]# abrt-cli list --since 1488267244 id ad716dbfd3a68bbe0f055e32ebfe562f4f75df43 reason: imap killed by SIGBUS time: Sun Mar 19 2017 10:58:27 AM JST cmdline: dovecot/imap package: dovecot-2.2.10-7.el7 uid: 80180 (acaa2325) count: 2 Directory:

Hi Chris, I've CC'd Eric Botcazou in the hope that he will clear up just what the Ada front-end needs from the rest of the compiler as far as asynchronous exceptions are concerned. >> gcc Ada turns signals into exceptions. As far as I know it does this >> completely asynchronously, and the fact that LLVM doesn't support this >> is rather bad as far as Ada is