[lldb-dev] lldb crash while debugging wxWidgets application that was built with g++

Enrico Granata egranata at apple.com
Tue Apr 8 14:01:21 PDT 2014


On Apr 8, 2014, at 1:49 PM, Eran Ifrah <eran.ifrah at gmail.com> wrote:

> Hi,
> 
> While debugging a real world application (codelite) I placed a breakpoint in the 'OnAbout' function
> attempting to view any of the local variables resulted in crash, see below:
> 
> Process 24146 stopped
> * thread #1: tid = 24146, 0x00000000006667f6 codelite`clMainFrame::OnAbout(this=0x000000000215f5c0, (null)=0x00007fffa6fd2640) + 66 at frame.cpp:1794, name = 'codelite', stop reason = step over
>     frame #0: 0x00000000006667f6 codelite`clMainFrame::OnAbout(this=0x000000000215f5c0, (null)=0x00007fffa6fd2640) + 66 at frame.cpp:1794
>    1791     wxString mainTitle;
>    1792     mainTitle = CODELITE_VERSION_STR;
>    1793
> -> 1794     AboutDlg dlg(this, mainTitle);
>    1795     dlg.SetInfo(mainTitle);
>    1796     dlg.ShowModal();
>    1797 }
> (lldb) p dlg
> error: libwx_gtk2u_unofficial_core-3.0.so.0 DWARF DIE at 0x030ac4cc for class 'wxSizer' has a base class 'wxClientDataContainer' that is a forward declaration, not a complete definition.
> Please file a bug against the compiler and include the preprocessed output for /home/david/devel/packages/wx/3.0-2/wxwidgets3.0-3.0.0/objs_gtk_sh/../src/common/sizer.cpp
> Segmentation fault
> 
> From the segfault message, I understand that this is a bug with gcc
> Still, is there a way to suppress this error by telling lldb to silently ignore this? ( I prefer it to display nothing instead of crashing and taking down codelite with it )
> 
> Thanks
> 
> -- 
> Eran Ifrah
> Author of codelite, a cross platform open source C/C++ IDE: http://www.codelite.org
> wxCrafter, a wxWidgets RAD: http://wxcrafter.codelite.org
> _______________________________________________
> lldb-dev mailing list
> lldb-dev at cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/lldb-dev


I don’t think we should be segfaulting.. would you be able to attach a debugger to your running codelite, and see where the segfault is being triggered?
That would be a good start of an investigation of this issue

- Enrico
📩 egranata@.com ☎️ 27683



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/lldb-dev/attachments/20140408/b4e95411/attachment.html>


More information about the lldb-dev mailing list