search for: sigbus

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 anything about it. It's sometimes hard to notice that that was caused by the lack of disk space. I wonder if we should print out a hint (e.g. "Bus error -...

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 > getting the signal directly, instead carefully handling the signal in LLD > itself and trans...

..., 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 >>> 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 >>> getting the signal directly, instead carefully handling the signal in L...

...lts. 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 months. This is the error I am seeing: Caught SIGBUS/SEGV while mmapping. File was truncated while aide was running? Caught SIGBUS/SEGV. Exiting I tried Googling for it, but didn't find anything helpful. Any ideas? -- Bowie

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_sca...

...; 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 anything about it. It's sometimes hard to > notice > > that that was caused by the lack of disk space. > > > >...

...32dfb8, 0x3 /1@1: -> liblber-2.3:ber_memfree_x(0x32dfd7, 0x0, 0x0, 0x0) /1@1: -> libc:free(0x32dfd7, 0x0, 0x0, 0x0) /1@1: -> libc:_free_unlocked(0x32dfd7, 0x0, 0x0, 0xfee3c000) /1: Incurred fault #5, FLTACCESS %pc = 0xFEDC7D80 /1: siginfo: SIGBUS BUS_ADRALN addr=0x0032DFCF ^^^^^^^ /1: Received signal #10, SIGBUS [caught] /1: siginfo: SIGBUS BUS_ADRALN addr=0x0032DFCF /1@1: -> libc:sigaddset(0xff...

...> >> 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 anything about it. It's sometimes hard to notice >> that that was caused by the lack of disk space. >> >> I...

-------- 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...

...32dfb8, 0x3 /1@1: -> liblber-2.3:ber_memfree_x(0x32dfd7, 0x0, 0x0, 0x0) /1@1: -> libc:free(0x32dfd7, 0x0, 0x0, 0x0) /1@1: -> libc:_free_unlocked(0x32dfd7, 0x0, 0x0, 0xfee3c000) /1: Incurred fault #5, FLTACCESS %pc = 0xFEDC7D80 /1: siginfo: SIGBUS BUS_ADRALN addr=0x0032DFCF ^^^^^^^ /1: Received signal #10, SIGBUS [caught] /1: siginfo: SIGBUS BUS_ADRALN addr=0x0032DFCF /1@1: -> libc:sigaddset(0xffbf...

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 alignment problem. I've appended a quick fix for this, which at least makes tinc not crash any more. Elrond -------------- next part -------------- --- route.c~ Thu Jul 31 15...

...and JASS and vigilant/paranoid sysadmins have been known to set a restricitve umask in /etc/default/login. OpenSSH compatibility for Solaris 8 has been spotty at times for sparcv9 targets. This time, when a sparcv9 binary tries to sscanf(3C) the numeric umask as a long octal and put it in a mode_t, SIGBUS happens. What this looks like in real life is: You are running a 64 bit OpenSSH_3.7.1p2 sshd on Solaris 8, and you have enforced UMASK in /etc/default/login. You try to log into this sshd, but after all the authentication and channel setup, just before you get your shell/command executed *POOF*. T...

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-chec...

...t; > > > > > 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: /var/spool/abrt/ccpp-2017-0...

...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 >> >...

...".., 8192) = 2010 8132: read(7, 0x100287C14, 8192) = 0 8132: lseek(7, 0, SEEK_CUR) = 2010 8132: close(7) = 0 8132: Incurred fault #5, FLTACCESS %pc = 0xFFFFFFFF7EC991C8 8132: siginfo: SIGBUS BUS_ADRALN addr=0xFFFFFFFF7FFFE334 8132: Received signal #10, SIGBUS [default] 8132: siginfo: SIGBUS BUS_ADRALN addr=0xFFFFFFFF7FFFE334 8128: Received signal #18, SIGCLD [caught] 8128: siginfo: SIGCLD CLD_KILLED pid=8132 status=0x000A 8128: fstat(-1, 0xFFFFFFFF7FFFD880...

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: /var/spool/abrt/ccpp-2017-03-19-10:58:27-4904 'abrt-cli report ?????/var/spool/abrt/ccpp-2017-03-19-10:58:27-4904...

...at LLVM doesn't support this >> is rather bad as far as Ada is concerned. That said, the Ada front-end > > You're saying that it turns asynch signals like SIGHUP (which can occur on any machine instruction) into signals? AFAIK, on posix systems only SIGFPE, SIGILL, SIGSEGV and SIGBUS are turned into exceptions. For other signals, if there is no signal handler then the program is terminated; if the user installed a signal handler then it is run, and as far as I know there is no way for a user installed handler to raise an exception at the original point of execution without goi...