From mboxrd@z Thu Jan  1 00:00:00 1970
Date: Tue, 27 Oct 2015 10:08:43 -0700 (PDT)
From: Juan RP <xtr...@gmail.com>
To: voidlinux <void...@googlegroups.com>
Message-Id: <402dd933-4175-47bf-9c63-7e94bd5c30a3@googlegroups.com>
In-Reply-To: <7923bb5f-4953-43f7-85a1-7c60b2d5366c@googlegroups.com>
References: <7923bb5f-4953-43f7-85a1-7c60b2d5366c@googlegroups.com>
Subject: Re: Segmentation fault following update
MIME-Version: 1.0
Content-Type: multipart/mixed; 
	boundary="----=_Part_723_1390669000.1445965723311"

------=_Part_723_1390669000.1445965723311
Content-Type: multipart/alternative; 
	boundary="----=_Part_724_83536803.1445965723311"

------=_Part_724_83536803.1445965723311
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit


Without more info it's hard to know what's going on.

You can run `gdb` and then dissassemble the faulty instruction.

Or run strace and see where it triggers the segmentation fault.

------=_Part_724_83536803.1445965723311
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 7bit

<div dir="ltr"><br>Without more info it&#39;s hard to know what&#39;s going on.<br><br>You can run `gdb` and then dissassemble the faulty instruction.<br><br>Or run strace and see where it triggers the segmentation fault.<br></div>
------=_Part_724_83536803.1445965723311--

------=_Part_723_1390669000.1445965723311--