* Segmentation fault following update
@ 2015-10-27 7:57 Jeremy Mason
2015-10-27 17:08 ` Juan RP
0 siblings, 1 reply; 3+ messages in thread
From: Jeremy Mason @ 2015-10-27 7:57 UTC (permalink / raw)
To: voidlinux
[-- Attachment #1.1: Type: text/plain, Size: 1078 bytes --]
Hello,
Yesterday I updated the system using
$ sudo xbps-install -Syu
and recieved a large number of updated packages, including the 4.1.11_1
version of the kernel. Since then, when trying to launch MATLAB, I always
get a segmentation fault:
$ /usr/local/MATLAB/R2015b/bin/matlab
MATLAB is selecting SOFTWARE OPENGL rendering.
Segmentation fault
I have never observed this happen before. I had a working installation of
MATLAB before the update, and reinstalling the program does not help. I
tried to figure out what is causing this with gdb:
$ matlab -Dgdb
MATLAB is selecting SOFTWARE OPENGL rendering.
GNU gdb (GDB) 7.10
...
(gdb) run
Starting program: /usr/local/MATLAB/R2015b/bin/glnxa64/MATLAB
-prefersoftwareopengl
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
Program received signal SIGSEGV, Segmentation fault.
0x0000000000000000 in ?? ()
So it looks like the issue could be with the threading library. At this
point I am not sure what to do. Any ideas?
Thank you for the help,
Jeremy Mason
[-- Attachment #1.2: Type: text/html, Size: 1196 bytes --]
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Segmentation fault following update
2015-10-27 7:57 Segmentation fault following update Jeremy Mason
@ 2015-10-27 17:08 ` Juan RP
2015-11-01 17:15 ` Jeremy Mason
0 siblings, 1 reply; 3+ messages in thread
From: Juan RP @ 2015-10-27 17:08 UTC (permalink / raw)
To: voidlinux
[-- Attachment #1.1: Type: text/plain, Size: 184 bytes --]
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.
[-- Attachment #1.2: Type: text/html, Size: 231 bytes --]
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Segmentation fault following update
2015-10-27 17:08 ` Juan RP
@ 2015-11-01 17:15 ` Jeremy Mason
0 siblings, 0 replies; 3+ messages in thread
From: Jeremy Mason @ 2015-11-01 17:15 UTC (permalink / raw)
To: voidlinux
[-- Attachment #1.1: Type: text/plain, Size: 461 bytes --]
This is apparently due to MATLAB breaking after upgrading ncurses to v6.x.
The problem has been diagnosed in some detail over in the Arch forums:
https://bbs.archlinux.org/viewtopic.php?id=202575
On Tuesday, October 27, 2015 at 8:08:43 PM UTC+3, Juan RP wrote:
>
>
> 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.
>
[-- Attachment #1.2: Type: text/html, Size: 655 bytes --]
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2015-11-01 17:15 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2015-10-27 7:57 Segmentation fault following update Jeremy Mason
2015-10-27 17:08 ` Juan RP
2015-11-01 17:15 ` Jeremy Mason
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).