# SIGABRT after throwing VisRTX::Exception in CentOS 6.10
**URL:** https://discourse.paraview.org/t/sigabrt-after-throwing-visrtx-exception-in-centos-6-10/2670
**Category:** ParaView Support
**Created:** [October 2, 2019, 3:05pm UTC](https://discourse.paraview.org/t/sigabrt-after-throwing-visrtx-exception-in-centos-6-10/2670 "2019-10-02T15:05:50Z")
**Posts on this page:** 7
**Page:** 1
### Author:  [@mr-reca](https://discourse.paraview.org/u/mr-reca)
#### Post date: [October 2, 2019, 3:05pm UTC](https://discourse.paraview.org/t/sigabrt-after-throwing-visrtx-exception-in-centos-6-10/2670/1 "2019-10-02T15:05:50Z")
Hi everyone,
I’ve just installed ParaView 5.7 (ParaView-5.7.0-RC4-MPI-Linux-Python3.7-64bit.tar.gz) in a CentOS 6.10. The machine comes with 2 P5000 GPU (configured now with SLI and drivers up to date from the official website) and when I run the binary to open the program, it shows me the following output:
```
terminate called after throwing an instance of 'VisRTX::Exception'
what(): Invalid value
Loguru caught a signal: SIGABRT
Stack trace:
46 0x40771d /opt/ParaView/v5.7.0/bin/paraview() [0x40771d]
45 0x344a01ed20 __libc_start_main + 256
44 0x407530 /opt/ParaView/v5.7.0/bin/paraview() [0x407530]
43 0x40c10b /opt/ParaView/v5.7.0/bin/paraview() [0x40c10b]
42 0x4085d9 /opt/ParaView/v5.7.0/bin/paraview() [0x4085d9]
41 0x7f89c6b032e8 pqParaViewBehaviors::pqParaViewBehaviors(QMainWindow*, QObject*) + 2760
40 0x7f89c6a84682 pqAlwaysConnectedBehavior::pqAlwaysConnectedBehavior(QObject*) + 226
39 0x7f89c6a84535 pqAlwaysConnectedBehavior::serverCheck() + 117
38 0x7f89c4ac3167 pqObjectBuilder::createServer(pqServerResource const&, int) + 199
37 0x7f89c275e179 vtkSMSession::ConnectToSelf(int) + 105
36 0x7f89c102943e vtkProcessModule::RegisterSession(vtkSession*) + 142
35 0x7f89b4e772a6 /opt/ParaView/v5.7.0/bin/../lib/libvtkCommonCore-pv5.7.so.1(+0x4302a6) [0x7f89b4e772a6]
34 0x7f89b4cca889 vtkCallbackCommand::Execute(vtkObject*, unsigned long, void*) + 25
33 0x7f89c4295d4c /opt/ParaView/v5.7.0/bin/../lib/libvtkGUISupportQt-pv5.7.so.1(+0x39d4c) [0x7f89c4295d4c]
32 0x7f89c4282527 /opt/ParaView/v5.7.0/bin/../lib/libvtkGUISupportQt-pv5.7.so.1(+0x26527) [0x7f89c4282527]
31 0x7f89c589ec47 QMetaObject::activate(QObject*, int, int, void**) + 1511
30 0x7f89c4a64b59 /opt/ParaView/v5.7.0/bin/../lib/libpqCore-pv5.7.so.1(+0x76b59) [0x7f89c4a64b59]
29 0x7f89c4a602d2 pqServerManagerObserver::connectionCreated(long long) + 50
28 0x7f89c589ec47 QMetaObject::activate(QObject*, int, int, void**) + 1511
27 0x7f89c4b0ee12 pqServerManagerModel::onConnectionCreated(long long) + 770
26 0x7f89c4a5f142 pqServerManagerModel::serverAdded(pqServer*) + 50
25 0x7f89c589ec47 QMetaObject::activate(QObject*, int, int, void**) + 1511
24 0x7f89c6ace169 pqDefaultViewBehavior::onServerCreation(pqServer*) + 585
23 0x7f89c4abe3fe pqObjectBuilder::createView(QString const&, pqServer*) + 158
22 0x7f89c2769b5b vtkSMSessionProxyManager::NewProxy(char const*, char const*, char const*) + 203
21 0x7f89c27698a4 vtkSMSessionProxyManager::NewProxy(vtkPVXMLElement*, char const*, char const*, char const*) + 324
20 0x7f89c3b75f15 vtkSMViewProxy::ReadXMLAttributes(vtkSMSessionProxyManager*, vtkPVXMLElement*) + 21
19 0x7f89c273406b vtkSMProxy::ReadXMLAttributes(vtkSMSessionProxyManager*, vtkPVXMLElement*) + 683
18 0x7f89c2735cdb vtkSMProxy::CreateSubProxiesAndProperties(vtkSMSessionProxyManager*, vtkPVXMLElement*) + 699
17 0x7f89c2733816 vtkSMProxy::NewProperty(char const*, vtkPVXMLElement*) + 422
16 0x7f89c279653c vtkSMStringVectorProperty::ReadXMLAttributes(vtkSMProxy*, vtkPVXMLElement*) + 28
15 0x7f89c27a0cc7 vtkSMVectorProperty::ReadXMLAttributes(vtkSMProxy*, vtkPVXMLElement*) + 23
14 0x7f89c271ffbf vtkSMProperty::ReadXMLAttributes(vtkSMProxy*, vtkPVXMLElement*) + 11871
13 0x7f89c3b3f2ce vtkSMRendererDomain::ReadXMLAttributes(vtkSMProperty*, vtkPVXMLElement*) + 30
12 0x7f89c3b3ee46 vtkSMRendererDomain::Update(vtkSMProperty*) + 54
11 0x7f89b2c6c264 vtkOSPRayPass::IsBackendAvailable(char const*) + 20
10 0x7f89b2c42856 /opt/ParaView/v5.7.0/bin/../lib/libvtkRenderingRayTracing-pv5.7.so.1(+0x1c856) [0x7f89b2c42856]
9 0x7f89b2c4273f /opt/ParaView/v5.7.0/bin/../lib/libvtkRenderingRayTracing-pv5.7.so.1(+0x1c73f) [0x7f89b2c4273f]
8 0x7f89b2c431a7 /opt/ParaView/v5.7.0/bin/../lib/libvtkRenderingRayTracing-pv5.7.so.1(+0x1d1a7) [0x7f89b2c431a7]
7 0x7f898cd862d9 VisRTX_GetContext + 5081
6 0x3450cbcd32 /usr/lib64/libstdc++.so.6() [0x3450cbcd32]
5 0x3450cbcc13 /usr/lib64/libstdc++.so.6() [0x3450cbcc13]
4 0x3450cbcbe6 /usr/lib64/libstdc++.so.6() [0x3450cbcbe6]
3 0x3450cbea8d __gnu_cxx::__ verbose_terminate_handler() + 301
2 0x344a033cd5 abort + 373
1 0x344a0324f5 gsignal + 53
0 0x344a032570 /lib64/libc.so.6() [0x344a032570]
( 0.668s) [paraview] :0 FATL| Signal: SIGABRT
```
I tried with another version (5.2) and the program works. I think the issue here is with the graphics, maybe with the X server or something with the GPU.
What should I do?
Kind regards,
---
### Author:  [@cory.quammen](https://discourse.paraview.org/u/cory.quammen)
#### Post date: [October 2, 2019, 5:35pm UTC](https://discourse.paraview.org/t/sigabrt-after-throwing-visrtx-exception-in-centos-6-10/2670/2 "2019-10-02T17:35:18Z")
@tbiedert Any advice on how to debug?
---
### Author:  [@tbiedert](https://discourse.paraview.org/u/tbiedert)
#### Post date: [October 2, 2019, 5:42pm UTC](https://discourse.paraview.org/t/sigabrt-after-throwing-visrtx-exception-in-centos-6-10/2670/3 "2019-10-02T17:42:54Z")
Would be good to know where exactly the exception is thrown.
Can you try building [VisRTX](https://github.com/NVIDIA/VisRTX) manually (in debug mode preferably) and test if you can run the basic sample application?
Thanks!
Tim
---
### Author:  [@mr-reca](https://discourse.paraview.org/u/mr-reca)
#### Post date: [October 4, 2019, 7:50am UTC](https://discourse.paraview.org/t/sigabrt-after-throwing-visrtx-exception-in-centos-6-10/2670/4 "2019-10-04T07:50:13Z")
Hi @tbiedert and @cory.quammen,
Thank you so much for your time. I’ll try to download the source and requirements and do an installation with verbose. I’ll send you the outputs of the build and the test as soon as possible.
Thanks,
---
### Author:  [@mr-reca](https://discourse.paraview.org/u/mr-reca)
#### Post date: [October 9, 2019, 2:21pm UTC](https://discourse.paraview.org/t/sigabrt-after-throwing-visrtx-exception-in-centos-6-10/2670/5 "2019-10-09T14:21:29Z")
Hi everyone,
I’m having some issues intalling CUDA 8, because it’s not detecting my nvidia drivers. I have installed 430.50, so it shoudl work.
I have downloaded OpticX and MDL SDK (also VisRTX), but I cannot install VisRTX until I have CUDA.
I’ll contact you as soon as I can. Thank you so much for your time,
---
### Author:  [@mr-reca](https://discourse.paraview.org/u/mr-reca)
#### Post date: [October 25, 2019, 8:10am UTC](https://discourse.paraview.org/t/sigabrt-after-throwing-visrtx-exception-in-centos-6-10/2670/6 "2019-10-25T08:10:38Z")
Hi there,
Sorry for not responding. I’m still having issues with CUDA 8 and the drivers.
Is there another way to test paraview?
Thank you so much,
---
### Author:  [@wascott](https://discourse.paraview.org/u/wascott)
#### Post date: [April 21, 2020, 10:41pm UTC](https://discourse.paraview.org/t/sigabrt-after-throwing-visrtx-exception-in-centos-6-10/2670/7 "2020-04-21T22:41:14Z")
Replicated. I wrote it up here: [https://gitlab.kitware.com/paraview/paraview/-/issues/19863](https://gitlab.kitware.com/paraview/paraview/-/issues/19863). I will get a debugger in it and see what is going on.