On 1/15/19 1:56 PM, David C. Rankin wrote:
(top post intentional)
Wohoo!!! With the release of 5.2.24 the problem is GONE!!!
There is still a problem with 6.0.0 BigTime, but whatever was botched in
6.0.0 is fixed in 5.2.24 and it compiles fine on Linux 4.20.1, Bash 5 and
Readline 8.
I'll try 6.0.2 later, but as long as 5.2 will remain supported for the next
year, I'll stay there until I can confirm 6 works.
On 01/15/2019 02:38 AM, Bruce Ferrell wrote:
Open a bug report?
quite possibly... You have the core file the resulted from that SIGABRT?
Someone may want to look at that to figure out what it was doing at the time
I'll have to find it, I don't recall where the coredump goes on Arch (if not,
it won't be hard to get another one) I can find the coredumpctl list and I can
use 'info' and 'gdb' to get the listings and registers. Though the PID is off
by a few numbers from the trace attach, though the times are relatively the
same. Here are both the 'info' and 'gdb' views of the coredump:
# coredumpctl --no-pager info 32429
PID: 32429 (VirtualBox)
UID: 1000 (david)
GID: 1060 (david)
Signal: 6 (ABRT)
Timestamp: Mon 2019-01-14 17:54:48 CST (9h ago)
Command Line: VirtualBox
Executable: /opt/VirtualBox/VirtualBox
Control Group: /user.slice/user-1000.slice/session-53.scope
Unit: session-53.scope
Slice: user-1000.slice
Session: 53
Owner UID: 1000 (david)
Boot ID: 17eacc054e58489b9d9e3125b6b4bc76
Machine ID: 537be4f3e9f842ab9c99453da7e20cae
Hostname: valkyrie
Storage:
/var/lib/systemd/coredump/core.VirtualBox.1000.17eacc054e58489b9d9e3125b6b4bc76.32429.1547510088000000.lz4
Message: Process 32429 (VirtualBox) of user 1000 dumped core.
Stack trace of thread 32429:
#0 0x00007f81d82a7d7f raise (libc.so.6)
#1 0x00007f81d8292672 abort (libc.so.6)
#2 0x00007f81d9da0d68 _ZNK14QMessageLogger5fatalEPKcz
(libQt5CoreVBox.so.5)
#3 0x00007f81d62afb1e
_ZN14QXcbConnectionC1EP19QXcbNativeInterfacebjPKc (libQt5XcbQpaVBox.so.5)
#4 0x00007f81d62b41b9
_ZN15QXcbIntegrationC1ERK11QStringListRiPPc (libQt5XcbQpaVBox.so.5)
#5 0x00007f81d65b94bc n/a (libqxcb.so)
#6 0x00007f81d95da128
_ZN27QPlatformIntegrationFactory6createERK7QStringRK11QStringListRiPPcS2_
(libQt5GuiVBox.so.5)
#7 0x00007f81d95ec51a n/a (libQt5GuiVBox.so.5)
#8 0x00007f81d95eda4f
_ZN22QGuiApplicationPrivate25createPlatformIntegrationEv (libQt5GuiVBox.so.5)
#9 0x00007f81d95ee2d0
_ZN22QGuiApplicationPrivate21createEventDispatcherEv (libQt5GuiVBox.so.5)
#10 0x00007f81d9f8bc62 _ZN23QCoreApplicationPrivate4initEv
(libQt5CoreVBox.so.5)
#11 0x00007f81d95f2c19 _ZN22QGuiApplicationPrivate4initEv
(libQt5GuiVBox.so.5)
#12 0x00007f81d8da7309 _ZN19QApplicationPrivate4initEv
(libQt5WidgetsVBox.so.5)
#13 0x0000000000443df7 n/a (VirtualBox)
#14 0x00000000004444d4 n/a (VirtualBox)
#15 0x00007f81d8294223 __libc_start_main (libc.so.6)
#16 0x00000000004438d9 n/a (VirtualBox)
# coredumpctl --no-pager gdb 32429
PID: 32429 (VirtualBox)
UID: 1000 (david)
GID: 1060 (david)
Signal: 6 (ABRT)
Timestamp: Mon 2019-01-14 17:54:48 CST (9h ago)
Command Line: VirtualBox
Executable: /opt/VirtualBox/VirtualBox
Control Group: /user.slice/user-1000.slice/session-53.scope
Unit: session-53.scope
Slice: user-1000.slice
Session: 53
Owner UID: 1000 (david)
Boot ID: 17eacc054e58489b9d9e3125b6b4bc76
Machine ID: 537be4f3e9f842ab9c99453da7e20cae
Hostname: valkyrie
Storage:
/var/lib/systemd/coredump/core.VirtualBox.1000.17eacc054e58489b9d9e3125b6b4bc76.32429.1547510088000000.lz4
Message: Process 32429 (VirtualBox) of user 1000 dumped core.
Stack trace of thread 32429:
#0 0x00007f81d82a7d7f raise (libc.so.6)
#1 0x00007f81d8292672 abort (libc.so.6)
#2 0x00007f81d9da0d68 _ZNK14QMessageLogger5fatalEPKcz
(libQt5CoreVBox.so.5)
#3 0x00007f81d62afb1e
_ZN14QXcbConnectionC1EP19QXcbNativeInterfacebjPKc (libQt5XcbQpaVBox.so.5)
#4 0x00007f81d62b41b9
_ZN15QXcbIntegrationC1ERK11QStringListRiPPc (libQt5XcbQpaVBox.so.5)
#5 0x00007f81d65b94bc n/a (libqxcb.so)
#6 0x00007f81d95da128
_ZN27QPlatformIntegrationFactory6createERK7QStringRK11QStringListRiPPcS2_
(libQt5GuiVBox.so.5)
#7 0x00007f81d95ec51a n/a (libQt5GuiVBox.so.5)
#8 0x00007f81d95eda4f
_ZN22QGuiApplicationPrivate25createPlatformIntegrationEv (libQt5GuiVBox.so.5)
#9 0x00007f81d95ee2d0
_ZN22QGuiApplicationPrivate21createEventDispatcherEv (libQt5GuiVBox.so.5)
#10 0x00007f81d9f8bc62 _ZN23QCoreApplicationPrivate4initEv
(libQt5CoreVBox.so.5)
#11 0x00007f81d95f2c19 _ZN22QGuiApplicationPrivate4initEv
(libQt5GuiVBox.so.5)
#12 0x00007f81d8da7309 _ZN19QApplicationPrivate4initEv
(libQt5WidgetsVBox.so.5)
#13 0x0000000000443df7 n/a (VirtualBox)
#14 0x00000000004444d4 n/a (VirtualBox)
#15 0x00007f81d8294223 __libc_start_main (libc.so.6)
#16 0x00000000004438d9 n/a (VirtualBox)
GNU gdb (GDB) 8.2.1
Copyright (C) 2018 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-pc-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /opt/VirtualBox/VirtualBox...(no debugging symbols
found)...done.
[New LWP 32429]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
Core was generated by `VirtualBox'.
Program terminated with signal SIGABRT, Aborted.
#0 0x00007f81d82a7d7f in raise () from /usr/lib/libc.so.6
(gdb) info frame
Stack level 0, frame at 0x7ffce2072830:
rip = 0x7f81d82a7d7f in raise; saved rip = 0x7f81d8292672
called by frame at 0x7ffce2072960
Arglist at 0x7ffce2072708, args:
Locals at 0x7ffce2072708, Previous frame's sp is 0x7ffce2072830
Saved registers:
rbx at 0x7ffce2072820, rip at 0x7ffce2072828
(gdb) quit
Ya know, I just ran across an article praising VirtualBox 6... Of course it was
for the UI, but one of the improvements is called out made me wonder:
"Hyper-V as a fallback execution core for windows hosts: This helps fix
problems running a 64 bit guest when Windows Security sandboxing is enabled"
I sort of think this is aimed at win 10, but might this be the source of the
problem?
Just musing...
_______________________________________________
VBox-users-community mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/vbox-users-community
_______________________________________________
Unsubscribe:
mailto:[email protected]?subject=unsubscribe
