Databases
StackOverflow2013
Postsdbo
POgdb: how to get a complete backtrace when fglrx_dri.so segfaults?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POgdb: how to get a complete backtrace when fglrx_dri.so segfaults?
    primarykey
    data
    text
    <p>I'm experiencing segmentation faults in the fglrx dri library when running my own Qt based OpenGL application. The backtrace I get from gdb (with dbg symbols installed for Qt and my own application):</p> <pre><code>Thread 1 (Thread 0xb7fd9720 (LWP 1809)): #0 0x06276705 in ?? () from /usr/lib/fglrx/dri/fglrx_dri.so #1 0x000020dc in ?? () #2 0x000020d9 in ?? () #3 0x00000000 in ?? () </code></pre> <p>I can not see where from my code I call the fglrx function which causes the segmentation fault. How could I extend this backtrace to see it completely from the main() function down to the fglrx dri library?</p> <p>edit: To confirm my own application is built with debug symbols:</p> <pre><code>Reading symbols from /home/user/fglrx crash/crashtest-build-desktop-Qt_4_8_1__Qt-4_8_1__Debug/crashtest...done. (gdb) br main Breakpoint 1 at 0x804996d: file ../program/main.cpp, line 21. (gdb) run Starting program: /home/user/fglrx crash/crashtest-build-desktop-Qt_4_8_1__Qt-4_8_1__Debug/crashtest [Thread debugging using libthread_db enabled] Breakpoint 1, main (argc=1, argv=0xbffff2a4) at ../program/main.cpp:21 21 QApplication a(argc, argv); (gdb) bt #0 main (argc=1, argv=0xbffff2a4) at ../program/main.cpp:21 (gdb) n [New Thread 0xb7d2bb70 (LWP 2475)] [New Thread 0xb752ab70 (LWP 2476)] 22 QMainWindow w; (gdb) bt #0 main (argc=1, argv=0xbffff2a4) at ../program/main.cpp:22 (gdb) s QFlags&lt;Qt::WindowType&gt;::QFlags (this=0xbffff164) at /usr/local/Trolltech/Qt-4.8.1/include/QtCore/qglobal.h:2284 2284 Q_DECL_CONSTEXPR inline QFlags(Zero = 0) : i(0) {} (gdb) bt #0 QFlags&lt;Qt::WindowType&gt;::QFlags (this=0xbffff164) at /usr/local/Trolltech/Qt-4.8.1/include/QtCore/qglobal.h:2284 #1 0x080499a4 in main (argc=1, argv=0xbffff2a4) at ../program/main.cpp:22 </code></pre>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USChristophe
    1. USChristophe
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POgdb: how to get a complete backtrace when fglrx_dri.so segfaults?
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POgdb: how to get a complete backtrace when fglrx_dri.so segfaults?
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POgdb: how to get a complete backtrace when fglrx_dri.so segfaults?
      1. This table or related slice is empty.
      1. VTUpMod
    1. This table or related slice is empty.
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload