request assistance for gdb and seg fault
by bkelly from LinuxQuestions.org on (#51BSE)
Centos, GNU bash 4.2.46(2)
I have a Qt project of moderate size, multiple dialogs. . I am unable to copy from that computer to here so that is an impediment.
The app crashes with Segmentation fault. The GDB backtrace command shows a stack of 21 elements
The stack frames output contains
Quote:
From main the two relevant lines are:
Code:150 strip_chart->show(); <<< this line is referenced
151 <blank line>
152 status = app.exec(); <<< not this oneAll the constructors have printf on entry and exit and show that all have exited. That supports the backtrace output. This runs from a timer that is currently inhibited so nothing "should" happen until there is a keyboard entry. It crashes before any entry can be made.
Is there any GDB command that might provide a clue as to where I might find my defect?
I have a Qt project of moderate size, multiple dialogs. . I am unable to copy from that computer to here so that is an impediment.
The app crashes with Segmentation fault. The GDB backtrace command shows a stack of 21 elements
The stack frames output contains
Quote:
| #0 " QWidgetItem::isEmpty() " #1 "QWidgetItem::sizeHint() " " #20 " at main.cpp:150 |
Code:150 strip_chart->show(); <<< this line is referenced
151 <blank line>
152 status = app.exec(); <<< not this oneAll the constructors have printf on entry and exit and show that all have exited. That supports the backtrace output. This runs from a timer that is currently inhibited so nothing "should" happen until there is a keyboard entry. It crashes before any entry can be made.
Is there any GDB command that might provide a clue as to where I might find my defect?