Here is the segfault log:

__ __ __ _ _ ____ _
| \/ |_ _ _ __ ___ _ __ / /_ | || | | _ \| |_ _ ___
| |\/| | | | | '_ \ / _ \ '_ \| '_ \| || |_| |_) | | | | / __|
| | | | |_| | |_) | __/ | | | (_) |__ _| __/| | |_| \__ \
|_| |_|\__,_| .__/ \___|_| |_|\___/ |_| |_| |_|\__,_|___/
|_| http://code.google.com/p/mupen64plus/
Version 1.5-development

Config Dir: /home/user/.mupen64plus/
Install Dir: /usr/share/mupen64plus/
Plugin Dir: /usr/lib/mupen64plus

Rescanning rom cache.
Scanning... /media/mmc1/ROMS/N64/
Rom cache up to date. 14 ROMs.
Compression: Uncompressed
Imagetype: .z64 (native)
Rom size: 8388608 bytes (or 8 Mb or 64 Megabits)
MD5: 45676429EF6B90E65B517129B700308E
80 37 12 40
ClockRate = f
Version: 1446
CRC: a03cf036 bcc1c5d2
Name: SUPER MARIO 64
Manufacturer: Nintendo
Cartridge_ID: 4d53
Country: Europe (0x50)
PC = 80241800
EEPROM type: 0
init timer!
[gles2n64]: Loading Config from /home/user/.mupen64plus/gles2n64.conf
[blight's SDL input plugin]: version 0.0.10 initialized.
init timer!
[gles2n64]: Loading Config from /home/user/.mupen64plus/gles2n64.conf
[blight's SDL input plugin]: version 0.0.10 initialized.
Segmentation fault

Here is the sigsegv log:

__ __ __ _ _ ____ _
| \/ |_ _ _ __ ___ _ __ / /_ | || | | _ \| |_ _ ___
| |\/| | | | | '_ \ / _ \ '_ \| '_ \| || |_| |_) | | | | / __|
| | | | |_| | |_) | __/ | | | (_) |__ _| __/| | |_| \__ \
|_| |_|\__,_| .__/ \___|_| |_|\___/ |_| |_| |_|\__,_|___/
|_| http://code.google.com/p/mupen64plus/
Version 1.5-development

Config Dir: /home/user/.mupen64plus/
Install Dir: /usr/share/mupen64plus/
Plugin Dir: /usr/lib/mupen64plus

Rescanning rom cache.
Scanning... /media/mmc1/ROMS/N64/
Rom cache up to date. 14 ROMs.
Compression: Uncompressed
Imagetype: .z64 (native)
Rom size: 8388608 bytes (or 8 Mb or 64 Megabits)
MD5: 45676429EF6B90E65B517129B700308E
80 37 12 40
ClockRate = f
Version: 1446
CRC: a03cf036 bcc1c5d2
Name: SUPER MARIO 64
Manufacturer: Nintendo
Cartridge_ID: 4d53
Country: Europe (0x50)
PC = 80241800
EEPROM type: 0
init timer!
[gles2n64]: Loading Config from /home/user/.mupen64plus/gles2n64.conf
[blight's SDL input plugin]: version 0.0.10 initialized.
init timer!
[gles2n64]: Loading Config from /home/user/.mupen64plus/gles2n64.conf
[blight's SDL input plugin]: version 0.0.10 initialized.
Error: The core thread recieved a SIGSEGV signal.
This means it tried to access protected memory.
Maybe you have set a wrong ucode for one of the plugins!
SIGSEGV in core thread caught:
errno = 0 (Success)
address = 0x73752F89
address not mapped to object
Error: The core thread recieved a SIGSEGV signal.
This means it tried to access protected memory.
Maybe you have set a wrong ucode for one of the plugins!
SIGSEGV in core thread caught:
errno = 0 (Success)
address = 0x73752F89
address not mapped to object
Error: The core thread recieved a SIGSEGV signal.
This means it tried to access protected memory.
Maybe you have set a wrong ucode for one of the plugins!
SIGSEGV in core thread caught:
errno = 0 (Success)
address = 0x73752F89
address not mapped to object
Error: The core thread recieved a SIGSEGV signal.
This means it tried to access protected memory.
Maybe you have set a wrong ucode for one of the plugins!
SIGSEGV in core thread caught:
errno = 0 (Success)
address = 0x73752F89
address not mapped to object
Error: The core thread recieved a SIGSEGV signal.
This means it tried to access protected memory.
Maybe you have set a wrong ucode for one of the plugins!
SIGSEGV in core thread caught:
errno = 0 (Success)
address = 0x73752F89
address not mapped to object
Error: The core thread recieved a SIGSEGV signal.
This means it tried to access protected memory.
Maybe you have set a wrong ucode for one of the plugins!
SIGSEGV in core thread caught:
errno = 0 (Success)
address = 0x73752F89
address not mapped to object
Error: The core thread recieved a SIGSEGV signal.
This means it tried to access protected memory.
Maybe you have set a wrong ucode for one of the plugins!
SIGSEGV in core thread caught:
errno = 0 (Success)
address = 0x73752F89
address not mapped to object
Error: The core thread recieved a SIGSEGV signal.
This means it tried to access protected memory.
Maybe you have set a wrong ucode for one of the plugins!
SIGSEGV in core thread caught:
errno = 0 (Success)
address = 0x73752F89
address not mapped to object
Error: The core thread recieved a SIGSEGV signal.
This means it tried to access protected memory.
Maybe you have set a wrong ucode for one of the plugins!
SIGSEGV in core thread caught:
errno = 0 (Success)
address = 0x73752F89
address not mapped to object
Error: The core thread recieved a SIGSEGV signal.
This means it tried to access protected memory.
Maybe you have set a wrong ucode for one of the plugins!
SIGSEGV in core thread caught:
errno = 0 (Success)
address = 0x73752F89
address not mapped to object
Error: The core thread recieved a SIGSEGV signal.
This means it tried to access protected memory.
Maybe you have set a wrong ucode for one of the plugins!
SIGSEGV in core thread caught:
errno = 0 (Success)
address = 0x73752F89
address not mapped to object
Error: The core thread recieved a SIGSEGV signal.
This means it tried to access protected memory.
Maybe you have set a wrong ucode for one of the plugins!
SIGSEGV in core thread caught:
errno = 0 (Success)
address = 0x73752F89
address not mapped to object
Error: The core thread recieved a SIGSEGV signal.
This means it tried to access protected memory.
Maybe you have set a wrong ucode for one of the plugins!
SIGSEGV in core thread caught:
errno = 0 (Success)
address = 0x73752F89
address not mapped to object
Error: The core thread recieved a SIGSEGV signal.
This means it tried to access protected memory.
Maybe you have set a wrong ucode for one of the plugins!
SIGSEGV in core thread caught:
errno = 0 (Success)
address = 0x73752F89
address not mapped to object
Error: The core thread recieved a SIGSEGV signal.
This means it tried to access protected memory.
Maybe you have set a wrong ucode for one of the plugins!
SIGSEGV in core thread caught:
errno = 0 (Success)
address = 0x73752F89
address not mapped to object
Killed

I have killed it from a ssh shell because it was flooding windows with error messages on the GUI.