On 08 Jan 2015, at 18:46 , Mark Johnston ma...@freebsd.org wrote:
On Thu, Jan 08, 2015 at 07:27:10PM +0100, Dimitry Andric wrote:
On 08 Jan 2015, at 16:24, Mark Johnston ma...@freebsd.org wrote:
On Thu, Jan 08, 2015 at 02:06:16PM +, Bjoern A. Zeeb wrote:
...
It only started 2 nights
On Thu, Jan 8, 2015 at 5:42 PM, Bjoern A. Zeeb
bzeeb-li...@lists.zabbadoz.net wrote:
On 08 Jan 2015, at 18:46 , Mark Johnston ma...@freebsd.org wrote:
On Thu, Jan 08, 2015 at 07:27:10PM +0100, Dimitry Andric wrote:
On 08 Jan 2015, at 16:24, Mark Johnston ma...@freebsd.org wrote:
On Thu, Jan
kernel.debug ...
Segmentation fault (core dumped)
*** [kernel.debug] Error code 139
...
I'm mostly wondering what Error code 139 is intended to mean :-}
It's the way termination due to a signal is reported. The exit status
is 128 + the signal number and SIGSEGV = 11.
I did see it twice
:
--- kernel.debug ---
linking kernel.debug
ctfmerge -L VERSION -g -o kernel.debug ...
Segmentation fault (core dumped)
*** [kernel.debug] Error code 139
...
I'm mostly wondering what Error code 139 is intended to mean :-}
It's the way termination due to a signal is reported. The exit
:
On 7 January 2015 at 08:57, David Wolfskill da...@catwhisker.org wrote:
--- kernel.debug ---
linking kernel.debug
ctfmerge -L VERSION -g -o kernel.debug ...
Segmentation fault (core dumped)
*** [kernel.debug] Error code 139
...
I'm mostly wondering what Error code 139 is intended
2015, at 14:13 , Ed Maste ema...@freebsd.org wrote:
On 7 January 2015 at 08:57, David Wolfskill da...@catwhisker.org wrote:
--- kernel.debug ---
linking kernel.debug
ctfmerge -L VERSION -g -o kernel.debug ...
Segmentation fault (core dumped)
*** [kernel.debug] Error code 139
...
I'm mostly
...
Segmentation fault (core dumped)
*** [kernel.debug] Error code 139
...
I'm mostly wondering what Error code 139 is intended to mean :-}
It's the way termination due to a signal is reported. The exit status
is 128 + the signal number and SIGSEGV = 11.
I did see it twice last night
On 08 Jan 2015, at 16:24, Mark Johnston ma...@freebsd.org wrote:
On Thu, Jan 08, 2015 at 02:06:16PM +, Bjoern A. Zeeb wrote:
...
It only started 2 nights ago and we are both doing daily builds. Unlikely
that stuff from November would do it oh so suddenly.
It’s hard to exactly narrow
On Thu, Jan 08, 2015 at 02:06:16PM +, Bjoern A. Zeeb wrote:
...
Ok, this continues; I have since seen it four more times. Still
i386.GENERIC only; none of the LINT kernels or other architectures.
Can someone please investigate what triggers this?
Looks like a stack overflow,
...
Segmentation fault (core dumped)
*** [kernel.debug] Error code 139
...
I'm mostly wondering what Error code 139 is intended to mean :-}
It's the way termination due to a signal is reported. The exit status
is 128 + the signal number and SIGSEGV = 11.
I did see it twice last night
On Thu, Jan 08, 2015 at 07:27:10PM +0100, Dimitry Andric wrote:
On 08 Jan 2015, at 16:24, Mark Johnston ma...@freebsd.org wrote:
On Thu, Jan 08, 2015 at 02:06:16PM +, Bjoern A. Zeeb wrote:
...
It only started 2 nights ago and we are both doing daily builds. Unlikely
that stuff
ctfconvert -L VERSION -g vers.o
--- kernel.debug ---
linking kernel.debug
ctfmerge -L VERSION -g -o kernel.debug ...
Segmentation fault (core dumped)
*** [kernel.debug] Error code 139
bmake: stopped in /common/S4/obj/usr/src/sys/GENERIC
1 error
bmake: stopped in /common/S4/obj/usr/src/sys/GENERIC
On 7 January 2015 at 08:57, David Wolfskill da...@catwhisker.org wrote:
--- kernel.debug ---
linking kernel.debug
ctfmerge -L VERSION -g -o kernel.debug ...
Segmentation fault (core dumped)
*** [kernel.debug] Error code 139
...
I'm mostly wondering what Error code 139 is intended to mean
On 07 Jan 2015, at 14:13 , Ed Maste ema...@freebsd.org wrote:
On 7 January 2015 at 08:57, David Wolfskill da...@catwhisker.org wrote:
--- kernel.debug ---
linking kernel.debug
ctfmerge -L VERSION -g -o kernel.debug ...
Segmentation fault (core dumped)
*** [kernel.debug] Error code 139
14 matches
Mail list logo
