Mercurial > hg > orthanc-book

comparison Sphinx/source/faq/crash.rst @ 244:26b0d7ece4af

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
debugging
author Sebastien Jodogne <s.jodogne@gmail.com>
date Mon, 13 May 2019 15:29:09 +0200
parents f277d18e8d71
children a64197133114
comparison
equal deleted inserted replaced
243:57ecb27d1851 244:26b0d7ece4af
1 .. _crash: 1 .. _crash:
2 2
3 Crash analysis 3 Crash analysis
4 ============== 4 ==============
5 5
6 If you experience a crash within Orthanc (or one of its plugins), that 6 Orthanc crashes very rarely. You are most likely looking for the FAQ
7 the troubleshooting sections (cf. :ref:`here <troubleshooting>` and 7 entry about :ref:`debugging Orthanc <debugging>`.
8 :ref:`here <dicom>`) do not help, and that you can't provide a robust
9 way to reproduce your issue by third-party developers, you'll have to
10 analyze the backtrace of Orthanc.
11 8
12 9
13 .. _segfault-plugin: 10 .. _segfault-plugin:
14 11
15 Generating a segmentation fault for test purpose 12 Generating a segmentation fault for test purpose
49 } 46 }
50 47
51 As soon as Orthanc will try and load this plugin, it will crash. This 48 As soon as Orthanc will try and load this plugin, it will crash. This
52 gives you the opportunity to learn how to debug Orthanc on your very 49 gives you the opportunity to learn how to debug Orthanc on your very
53 specific platform. 50 specific platform.
54
55
56 Any system
57 ----------
58
59 First :ref:`compile Orthanc by yourself <compiling>`, in debug mode by
60 setting ``-DCMAKE_BUILD_TYPE=Debug`` when invoking CMake.
61
62 Then, learn how to use the debugger that is best suited to your
63 platform (e.g. Microsoft Visual Studio, gdb or Xcode).
64 51
65 52
66 GNU/Linux system using gdb 53 GNU/Linux system using gdb
67 -------------------------- 54 --------------------------
68 55
110 <https://groups.google.com/forum/#!forum/orthanc-users>`__. 97 <https://groups.google.com/forum/#!forum/orthanc-users>`__.
111 98
112 **Important:** The Orthanc developers will only be able to analyze the 99 **Important:** The Orthanc developers will only be able to analyze the
113 ``core`` files generated by our own precompiled binaries! 100 ``core`` files generated by our own precompiled binaries!
114 101
115 **Plugins:** Besides the Orthanc core, debug binaries of the official
116 plugins precompiled using the LSB are also available at the following
117 locations:
118
119 * `Orthanc core <http://lsb.orthanc-server.com/orthanc/debug/>`__
120 * `DICOMweb plugin <http://lsb.orthanc-server.com/plugin-dicom-web/debug/>`__
121 * `MySQL plugin <http://lsb.orthanc-server.com/plugin-mysql/debug/>`__
122 * `Orthanc Web viewer <http://lsb.orthanc-server.com/plugin-webviewer/debug/>`__
123 * `PostgreSQL plugin <http://lsb.orthanc-server.com/plugin-postgresql/debug/>`__
124 * `Transfers accelerator plugin <http://lsb.orthanc-server.com/plugin-transfers/debug/>`__
125 * `Whole-slide imaging <http://lsb.orthanc-server.com/whole-slide-imaging/debug/>`__
126
127 102
128 Docker 103 Docker
129 ------ 104 ------
130 105
131 To be written. 106 To be written.