[lldb-dev] IOHandler branch has been merged into top of tree
Todd Fiala
tfiala at google.com
Thu Jan 30 12:41:24 PST 2014
The bug that I just fixed with ScriptInterpreterPython reference counting
of stdin/stderr/stdout *appears* to have fixed the libedit/libreadline
issues we were initially investigating :-)
That now maybe makes more sense in light of the fix since it may have been
trying to do something with a file (maybe via a weak reference) that really
should have been dead at that point.
At this point I have no more test failures on top of tree lldb at r200486.
On Wed, Jan 29, 2014 at 9:37 AM, Greg Clayton <gclayton at apple.com> wrote:
> RTTI is disabled in all the llvm/clang/lldb builds. When something is
> looking for typeinfo, it tends to mean some file was compiled thinking RTTI
> was enabled.
>
> On Jan 29, 2014, at 8:31 AM, Abid, Hafiz <Hafiz_Abid at mentor.com> wrote:
>
> > I am getting these error when building with cmake. Autoconf seems ok.
> Any idea what can be the problem?
> >
> > ../../../../lib/liblldb.so.3.5: undefined reference to `typeinfo for
> llvm::ModulePass'
> > ../../../../lib/liblldb.so.3.5: undefined reference to `typeinfo for
> clang::ExternalASTSource'
> > ../../../../lib/liblldb.so.3.5: undefined reference to `typeinfo for
> llvm::JITMemoryManager'
> > ../../../../lib/liblldb.so.3.5: undefined reference to `typeinfo for
> clang::ASTImporter'
> > ../../../../lib/liblldb.so.3.5: undefined reference to `typeinfo for
> clang::DiagnosticConsumer'
> > ../../../../lib/liblldb.so.3.5: undefined reference to `typeinfo for
> llvm::MemoryObject'
> > ../../../../lib/liblldb.so.3.5: undefined reference to `typeinfo for
> clang::SemaConsumer'
> >
> > Regards,
> > Abid
> >
> >> -----Original Message-----
> >> From: lldb-dev-bounces at cs.uiuc.edu [mailto:lldb-dev-bounces at cs.uiuc.edu
> ]
> >> On Behalf Of Greg Clayton
> >> Sent: 27 January 2014 23:51
> >> To: lldb-dev at cs.uiuc.edu
> >> Subject: [lldb-dev] IOHandler branch has been merged into top of tree
> >>
> >> We will need everyone to make sure their buildbots are ok and get any
> >> issues fixed. This is the one and only time the input/output and error
> >> streams will be changed in this drastic of a way. The benefits are many:
> >>
> >> 1 - Input/Output/Error streams are now handled as real streams not a
> push
> >> style input
> >> 2 - auto completion in python embedded interpreter
> >> 3 - multi-line input for "script" and "expression" commands now allow
> you
> >> to edit previous/next lines using up and down arrow keys and this makes
> >> multi-line input actually a viable thing to use
> >> 4 - it is now possible to use curses to drive LLDB (please try the "gui"
> >> command)
> >>
> >> We will need to deal with and fix any buildbot failures and tests and
> arise
> >> now that input/output and error are correctly hooked up in all cases.
> >>
> >> Greg Clayton
> >>
> >> _______________________________________________
> >> lldb-dev mailing list
> >> lldb-dev at cs.uiuc.edu
> >> http://lists.cs.uiuc.edu/mailman/listinfo/lldb-dev
>
> _______________________________________________
> lldb-dev mailing list
> lldb-dev at cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/lldb-dev
>
--
Todd Fiala | Software Engineer | tfiala at google.com | 650-943-3180
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/lldb-dev/attachments/20140130/d840fa3f/attachment.html>
More information about the lldb-dev
mailing list