-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
sumo-gui segmentation fault in Mac OS Catalina #6242
Comments
We're presently running a competition on CodaLab with users using sumo as a backend. We have around five teams experiencing this problem. Here's one of the threads we are using to debug the issue: https://competitions.codalab.org/forums/18353/3060/. and here's a relevant console output, process: sumo-gui [4935]
Path: /usr/local/Cellar/sumo/1.3.1/bin/sumo-gui
Identifier: sumo-gui
Version: 0
Code Type: X86-64 (Native)
Parent Process: zsh [3183]
Responsible: iTerm2 [3006]
User ID: 501
Date/Time: 2019-11-06 23:21:26.537 +0000
OS Version: Mac OS X 10.15.1 (19B88)
Report Version: 12
Bridge OS Version: 4.1 (17P1081)
Time Awake Since Boot: 4600 seconds
System Integrity Protection: enabled
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: EXC_I386_GPFLT
Exception Note: EXC_CORPSE_NOTIFY
Termination Signal: Segmentation fault: 11
Termination Reason: Namespace SIGNAL, Code 0xb
Terminating Process: exc handler [4935]
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 libdyld.dylib 0x00007fff6ea2f386 stack_not_16_byte_aligned_error + 0
1 ??? 0x00007ffee658d180 0 + 140732763001216
2 sumo-gui 0x000000010973d38e GUIIconSubSys::initIcons(FX::FXApp*) + 34
3 sumo-gui 0x0000000109679516 GUIApplicationWindow::GUIApplicationWindow(FX::FXApp*, std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&) + 554
4 sumo-gui 0x000000010967887c main + 620
5 libdyld.dylib 0x00007fff6ea3e2e5 start + 1
Thread 1:
0 libsystem_pthread.dylib 0x00007fff6ec4756c start_wqthread + 0
Thread 2:
0 libsystem_pthread.dylib 0x00007fff6ec4756c start_wqthread + 0
Thread 0 crashed with X86 Thread State (64-bit):
rax: 0x0000000000012138 rbx: 0x00007fec34f66850 rcx: 0x00007fec34f6687c rdx: 0x00007fec34f66878
rdi: 0x0000000109b29ab0 rsi: 0x00007fec34f66880 rbp: 0x00007ffee658d180 rsp: 0x00007ffee658d0e8
r8: 0x0000000000000001 r9: 0x0000000000000001 r10: 0x00007ffee658dbb8 r11: 0x000000010a8d5030
r12: 0x00007ffee658d230 r13: 0x00007fec37853248 r14: 0x0000000109b29ab0 r15: 0x00007fec37853400
rip: 0x00007fff6ea2f386 rfl: 0x0000000000010202 cr2: 0x000000010a9074fe
Logical CPU: 0
Error Code: 0x00000000
Trap Number: 13 |
Sorry we do not have Catalina systems here to test. So it might take some time and will definitely not be solved before the competition ends. |
Turns out Homebrew defaults to attempting to use existing bottles for newer macOS versions. Until a Catalina bottle has been added to the formula, the current workaround is to compile sumo on Catalina yourself (which worked for me, at least):
|
@schwamborn Unfortunately, it doesn't work for me. I still get the segmentation fault |
In that case, please post the output of:
|
SUMO_HOME is not defined. If I define it, it still fails.
The output of the original homebrew pkg uninstallation is:
The output of
|
Did you install XQuartz? If not: |
@schwamborn yes, XQuartz is installed and working. |
And I assume your XQuartz is also running fine? Might as well try a reinstall of XQuartz. |
Yes, it looks like XQuartz is running fine. For example,
|
Could finally reproduce the error and the sumo debug build gave these hints:
After some digging, it looks like there is something seriously wrong with Xcode 11 which might have led to a faulty Catalina bottle of libfox (a requirement for sumo-gui and netedit). For now, a quick and dirty workaround would be to downgrade to the Mojave bottle of fox:
Comment out or delete the following line:
This should also work with the Mojave bottle of sumo v1.3.1. I'm afraid that until this issue has been properly resolved, there won't be any Catalina bottle for sumo. |
@schwamborn great! It works ;). Thanks for the workaround |
Same problem, solved as @schwamborn said! Thank you. ;) |
problem not on our end. |
@schwamborn I am unable to comment or delete sha256 "c6697be294c9a0458580564d59f8db32791beb5e67a05a6246e0b969ffc068bc" => :catalina on brew edit fox. It is not letting to type. |
You need to enter edit mode which you can by pressing Shift + I, then add # to the start of each line and then finally press ESC and navigate to the bottom to type :x and press enter, this will save the changes you just made. |
Thanks a lot @schwamborn. It fixed the issue. |
With MacOS Catalina and XQuartz 2.7.11, if I try to run
sumo-gui
(with or without the-c
argument) I get:I installed sumo (version 1.3.1) using homebrew.
The text was updated successfully, but these errors were encountered: