| |
Kruthers
Registered: Jul 2016
Posts: 21 |
Segfault from Vice on Linux Mint 18
Saw the post about Vice and Ubuntu 16.04 and that reminds me, I upgraded to Linux Mint 18 which is based on that Ubuntu and after that my custom compiled x64sc would only segfault.
I recompiled on the new OS from a clean, freshly checked out svn copy and I still got segfaults. Finally figured out the cause was the --with-uithreads flag to configure; without that it's fine. This was just a few days ago.
Doesn't really seem like the fault of Vice - it worked fine under Mint 17 with that flag. But anyone have ideas how to get uithreads working again? |
|
| |
Firehawk
Registered: Aug 2011
Posts: 31 |
I found a problem with a lib_free of a temporary variable (main.c:241), apparently the code manages to overwrite the memory, thereby corrupting the next memory segment. If you set the malloc size (main.c:225) to a higher value (i.e. 250, since we do have a LOT of memory these days), the problem disapeared for me. |
| |
Compyx
Registered: Jan 2005
Posts: 631 |
@Kruthers: Could you post the issue on the bug tracker? https://sourceforge.net/p/vice-emu/bugs/
@Firehawk: I saw your bug report and I'm working on it. |
| |
Kruthers
Registered: Jul 2016
Posts: 21 |
@Firehawk: Damn you really had my hopes up! But no, that didn't do the trick in my case.
@Compyx: Definitely. I realize this isn't the vice support forums but figured somebody probably ran across the same problem... |
| |
Compyx
Registered: Jan 2005
Posts: 631 |
@Kruthers: thanks for using the bug tracker, looking into it now. |
| |
Kruthers
Registered: Jul 2016
Posts: 21 |
For anyone else that comes across this problem, it was an nvidia driver issue.
https://sourceforge.net/p/vice-emu/bugs/789/#fa99 |
| |
Marq
Registered: Sep 2011
Posts: 50 |
How about: export __GL_WRITE_TEXT_SECTION=0
Which fixes a - possibly related - crash with FS-UAE. |
| |
Compyx
Registered: Jan 2005
Posts: 631 |
Quote: How about: export __GL_WRITE_TEXT_SECTION=0
Which fixes a - possibly related - crash with FS-UAE.
Tried it, still segfaults. What is it supposed to do? Disable self modifying code in the driver? (Tried this with 304.131, which is all I can test, don't have any modern nvidia card) |
| |
Marq
Registered: Sep 2011
Posts: 50 |
Quote: Tried it, still segfaults. What is it supposed to do? Disable self modifying code in the driver? (Tried this with 304.131, which is all I can test, don't have any modern nvidia card)
It was worth a try anyway :) Dunno what it does in practice, but FS-UAE started crashing recently and that fixed it on Nvidia (352.63). |
| |
Compyx
Registered: Jan 2005
Posts: 631 |
From what I understand nvidia drivers use self-modifying code, which is of course the way to go on our favourite machine, but a pretty big no-no on modern operating systems.
The only consistent behaviour I can get from my nvidia card with binary drivers is that it crashes often and sometimes not.
The open source nouveau driver works much more reliably, although performance is still not quite like the binary drivers. But at least it doesn't crash. |
