Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 1 May 2020 05:16:05 +0200
From:      Polytropon <freebsd@edvax.de>
To:        David Christensen <dpchrist@holgerdanske.com>
Cc:        freebsd-questions@freebsd.org
Subject:   Re: Strange =?UTF-8?Q?bea=E2=94=82hio?= in daily messsges
Message-ID:  <20200501051605.05339635.freebsd@edvax.de>
In-Reply-To: <2a178278-fd90-189e-edcd-dbe224ea94d5@holgerdanske.com>
References:  <20200430044801.GA22722@mithril.foucry.net> <2a178278-fd90-189e-edcd-dbe224ea94d5@holgerdanske.com>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help
On Thu, 30 Apr 2020 12:22:03 -0700, David Christensen wrote:
> It appears signal 10 is a bus error:
> 
> https://github.com/freebsd/freebsd/blob/master/sys/sys/signal.h

No need to reference external GitHub resources - the local
documentation provided by the OS has the required information.
>From "man 3 signal":

     No    Name         Default Action       Description

     10    SIGBUS       create core image    bus error

And there's always /usr/include/sys/signal.h containing the
same information. :-)



> This page clarifies the meaning of "bus error":
> 
> https://www.geeksforgeeks.org/segmentation-fault-sigsegv-vs-bus-error-sigbus/
> 
> 
> My guess would be the latter case -- unaligned memory access.  This 
> could be a coding bug (struct not laid out for 64-bit architecture?) or 
> a misconfigured compile (?).

Sometimes, defective RAM (or something related to RAM) also
leads to SIGBUS, but in most cases, that is more of a
"surprise error", rather than a "predictable error".




-- 
Polytropon
Magdeburg, Germany
Happy FreeBSD user since 4.0
Andra moi ennepe, Mousa, ...



Want to link to this message? Use this URL: <http://docs.FreeBSD.org/cgi/mid.cgi?20200501051605.05339635.freebsd>