If I revert Greg Clayton's change r220113, then the core dump problem
vanishes.
I also found that running with r220113, but with the invocations of
SetAsync(True) removed, see below:
===================================================================
--- test/python_api/event/TestEvents.py (revision 220282)
+++ test/python_api/event/TestEvents.py (working copy)
@@ -67,7 +67,7 @@
"""Create a listener and use SBEvent API to print the events
received."""
exe = os.path.join(os.getcwd(), "a.out")
- self.dbg.SetAsync(True)
+# self.dbg.SetAsync(True)
# Create a target by the debugger.
target = self.dbg.CreateTarget(exe)
@@ -142,7 +142,7 @@
"""Get the listener associated with the debugger and exercise
WaitForEvent API."""
exe = os.path.join(os.getcwd(), "a.out")
- self.dbg.SetAsync(True)
+# self.dbg.SetAsync(True)
# Create a target by the debugger.
target = self.dbg.CreateTarget(exe)
@@ -211,7 +211,7 @@
"""Get the broadcaster associated with the process and wait for
broadcaster events."""
exe = os.path.join(os.getcwd(), "a.out")
- self.dbg.SetAsync(True)
+# self.dbg.SetAsync(True)
# Create a target by the debugger.
target = self.dbg.CreateTarget(exe)
also fixes the core dump, but leaves us with a couple of failing cases.
Greg, could you fix this, so that your change does not have to be
reverted in order to get the linux python tests to run?
thanks
Matt
On Tue, 2014-10-21 at 11:37 +0100, Matthew Gardiner wrote:
> Sorry, I forgot to mention, the core dump emanates from the failed
> assertion below:
>
>
> UNSUPPORTED: LLDB (gcc-x86_64) ::
> test_add_listener_to_broadcaster_with_dsym (TestEvents.EventAPITestCase)
> (requires Darwin)
> python:
> /home/mg11/src/vendor/llvm/tools/lldb/source/Plugins/Process/POSIX/ProcessPOSIX.cpp:270:
> virtual lldb_private::Error ProcessPOSIX::DoResume(): Assertion `state ==
> eStateStopped' failed.
> Aborted (core dumped)
>
>
> Matt
>
>
> On Tue, 2014-10-21 at 10:50 +0100, Matthew Gardiner wrote:
> > Hi all,
> >
> > In a build on 64-bit linux from TOT, I'm experiencing the test case
> > "TestEvents" causing python to segfault.
> >
> > I believe this to be a fairly recent regression. Anyone else seeing
> > this/or know what's responsible?
> >
> > I'm starting to analyse this...
> >
> > Matt
> >
> >
> >
> >
> >
> >
> > Member of the CSR plc group of companies. CSR plc registered in England and
> > Wales, registered number 4187346, registered office Churchill House,
> > Cambridge Business Park, Cowley Road, Cambridge, CB4 0WZ, United Kingdom
> > More information can be found at www.csr.com. Keep up to date with CSR on
> > our technical blog, www.csr.com/blog, CSR people blog, www.csr.com/people,
> > YouTube, www.youtube.com/user/CSRplc, Facebook,
> > www.facebook.com/pages/CSR/191038434253534, or follow us on Twitter at
> > www.twitter.com/CSR_plc.
> > New for 2014, you can now access the wide range of products powered by aptX
> > at www.aptx.com.
> > _______________________________________________
> > lldb-dev mailing list
> > lldb-dev@cs.uiuc.edu
> > http://lists.cs.uiuc.edu/mailman/listinfo/lldb-dev
> >
> >
> > To report this email as spam click
> > https://www.mailcontrol.com/sr/ZI1oLgnDwMzGX2PQPOmvUqy!8K4P2+30IvsLG52x8uGt4ohdor1WV8cxPonRMIDN8N3Z3vdBo3eVGm43FW9a3A==
> > .
>
>
> _______________________________________________
> lldb-dev mailing list
> lldb-dev@cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/lldb-dev
_______________________________________________
lldb-dev mailing list
lldb-dev@cs.uiuc.edu
http://lists.cs.uiuc.edu/mailman/listinfo/lldb-dev
