| | 54 | Experimenting with running VBoxSVC manually does this: |
| | 55 | |
| | 56 | |
| | 57 | {{{ |
| | 58 | # /usr/lib/virtualbox/VBoxSVC |
| | 59 | ************************************************ |
| | 60 | Oracle VM VirtualBox XPCOM Server Version 5.0.26 |
| | 61 | (C) 2004-2016 Oracle Corporation |
| | 62 | All rights reserved. |
| | 63 | |
| | 64 | Starting event loop.... |
| | 65 | [press Ctrl-C to quit] |
| | 66 | }}} |
| | 67 | |
| | 68 | The moment I run virtualbox in another window, the foreground VBoxSVC segfaults: |
| | 69 | |
| | 70 | |
| | 71 | {{{ |
| | 72 | # /usr/lib/virtualbox/VBoxSVC |
| | 73 | ************************************************ |
| | 74 | Oracle VM VirtualBox XPCOM Server Version 5.0.26 |
| | 75 | (C) 2004-2016 Oracle Corporation |
| | 76 | All rights reserved. |
| | 77 | |
| | 78 | Starting event loop.... |
| | 79 | [press Ctrl-C to quit] |
| | 80 | Segmentation fault |
| | 81 | }}} |
| | 82 | |
| | 83 | So this appears to be a fundamental programming error on your part as the program is trying to access memory across a byte boundary, (always a no no, no matter what architecture) |
| | 84 | |
| | 85 | |
