Bug 712715
Summary: | [abrt] gdb-7.2.90.20110525-38.fc15: get_type_arch: Process /usr/bin/gdb was killed by signal 11 (SIGSEGV) | ||||||
---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Stefano Tognon <ice00> | ||||
Component: | gdb | Assignee: | Phil Muldoon <pmuldoon> | ||||
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
Severity: | unspecified | Docs Contact: | |||||
Priority: | unspecified | ||||||
Version: | 15 | CC: | dodji, jan.kratochvil, pmuldoon, sergiodj, tromey | ||||
Target Milestone: | --- | ||||||
Target Release: | --- | ||||||
Hardware: | x86_64 | ||||||
OS: | Unspecified | ||||||
Whiteboard: | abrt_hash:f91f061ca483e372f88cb24f9a99625b2f1220a0 | ||||||
Fixed In Version: | gdb-7.3.1-47.fc15 | Doc Type: | Bug Fix | ||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2011-08-23 20:21:11 UTC | Type: | --- | ||||
Regression: | --- | Mount Type: | --- | ||||
Documentation: | --- | CRM: | |||||
Verified Versions: | Category: | --- | |||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
Cloudforms Team: | --- | Target Upstream Version: | |||||
Embargoed: | |||||||
Attachments: |
|
Description
Stefano Tognon
2011-06-12 16:42:08 UTC
Created attachment 504322 [details]
File: maps
:#2 0x00000000005e1d2d in value_get_print_value () at ../../gdb/varobj.c:2644 : type = 0x0 : string_print = 1 It seems clear to me there is a bug but I do not have a reproducer. This may be related to: http://sourceware.org/bugzilla/show_bug.cgi?id=12531 Where CPLUS_FAKE_CHILD objects (ie synthetic varobjs, not representing real C++ elements) are being worked on as if they were "real" data. Do you know if you were using the libstdc ++ pretty-printers in the session? Is it possible to condense a test-case or a similar use-case I can work with? What in fact is happening is the type associated with the value is 0x0 so subsequent operations fail. A Value (or a varobj containing a value) cannot have a 0x0 type. >Do you know if you were using the libstdc ++ pretty-printers in the session? Sorry I don't know what is libstdc ++ pretty-printers (this is first time I listen to it). >Is it possible to condense a test-case or a similar use-case I can work with? I had try but not able to produce a little case for test. The problem is on my project I'm converting from QT3 to Qt4: http://sourceforge.net/projects/xsidplay2/ With revision 104 the error comes every time. I set up a breakpoint into the first instruction of program: ############# part of code xsidplay.cpp ########## int main ( int argc, char** argv ) { QApplication a ( argc,argv ); player = new Player; ##################################### So on QApplication a ( argc,argv ); The debugger apparently stop into that point as I can see for a while stack frames and variables, then I get the segmentation fault from my program (and so it was not stopped as I expect) and less that five seconds after I get the gdb crash. With actual code it just needs to uncomment this instructions: setButtons(); from here: ########### part of code from FilterDialog.cpp ##### FilterDialog::FilterDialog(QWidget* parent) : FilterDialogData(parent) { setWindowIcon(*mainIcon); enableChangedSignal(true); ///setButtons(); paintFilterFunc(); } ############################################## for having the bug triggered on. As it it too complicated for you setting up my enviroments (xsidplay2 need many not common library for running), let me known if you have something for me to do that can help for bug finding. thanks I have committed a fix for this upstream to GDB. It will appear in Fedora in the next update http://sourceware.org/ml/gdb-cvs/2011-07/msg00234.html gdb-7.3.50.20110722-4.fc16 has been submitted as an update for Fedora 16. https://admin.fedoraproject.org/updates/gdb-7.3.50.20110722-4.fc16 Package gdb-7.3.50.20110722-4.fc16: * should fix your issue, * was pushed to the Fedora 16 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing gdb-7.3.50.20110722-4.fc16' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/gdb-7.3.50.20110722-4.fc16 then log in and leave karma (feedback). gdb-7.3.50.20110722-6.fc16 has been submitted as an update for Fedora 16. https://admin.fedoraproject.org/updates/gdb-7.3.50.20110722-6.fc16 gdb-7.3.50.20110722-6.fc16 has been pushed to the Fedora 16 stable repository. If problems still persist, please make note of it in this bug report. gdb-7.3.1-47.fc15 has been submitted as an update for Fedora 15. https://admin.fedoraproject.org/updates/gdb-7.3.1-47.fc15 gdb-7.3.1-47.fc15 has been pushed to the Fedora 15 stable repository. If problems still persist, please make note of it in this bug report. |