Re: [lldb-dev] issue with lldb9 and python3.5

2019-10-28 Thread Ted Woodward via lldb-dev 
Internally on Windows we use Python 3.5.1. I just ran our latest nightly, and 
was able to run the script interpreter in lldb without issues.

I want to upgrade to 3.7.x, but I need to get permission from our lawyers to 
ship it. Looking forward to that…

From: lldb-dev  On Behalf Of Adrian McCarthy 
via lldb-dev
Sent: Monday, October 28, 2019 12:10 PM
To: Jonas Devlieghere 
Cc: Serge Guelton ; LLDB Dev 
Subject: [EXT] Re: [lldb-dev] issue with lldb9 and python3.5

+1 Yes, for Windows, I'd be happy if we said Python 3.6+.

On Mon, Oct 28, 2019 at 10:07 AM Jonas Devlieghere via lldb-dev 
mailto:lldb-dev@lists.llvm.org>> wrote:
On Mon, Oct 28, 2019 at 10:04 AM Jonas Devlieghere
mailto:jo...@devlieghere.com>> wrote:
>
> On Mon, Oct 28, 2019 at 9:32 AM Tom Stellard 
> mailto:tstel...@redhat.com>> wrote:
> >
> > On 10/28/2019 09:29 AM, Jonas Devlieghere wrote:
> > > Yes, Python 3.5 is not supported. We "officially" support Python 2.7
> > > and Python 3.7. I'm sorry if we forgot that in the release notes.
> > >
> >
> > Is there a specific reason why 3.5 is not supported?  Is it
> > because of this issue?
>
> Not really other than the lack of testing/CI.
>
> - The Linux bots are all running with Python 2.7.
> - I know that on macOS we ran into issues with some older versions. I
> don't remember if it was this particular issue and I'm not even sure
> if that was using Python 3.5 or Python 3.6. Our bots on GreenDragon
> all run with Python 3.7.
> - Stella's Windows bot is running Python 3.6 so we should consider
> that supported as well.

For completeness, Python 2.7 is not supported on Windows at all. The
docs specify Python 3.5 or later. Maybe we should bump that to 3.6
too?

>
> >
> > -Tom
> >
> > > On Mon, Oct 28, 2019 at 7:06 AM Tom Stellard via lldb-dev
> > > mailto:lldb-dev@lists.llvm.org>> wrote:
> > >>
> > >> + lldb-dev
> > >>
> > >> On 10/28/2019 07:06 AM, Tom Stellard wrote:
> > >>> On 10/28/2019 03:50 AM, Romaric Jodin via lldb-dev wrote:
> >  Hi everyone,
> > 
> >  I have lldb crashing since I've updated to lldb9. Seems like there is 
> >  a issue with python3.5. Everything seems to work fine with python3.7.
> >  Am I missing something? Or is it a known issue?
> > 
> > >>>
> > >>> We have seen this too with python 3.6, but we haven't found the root 
> > >>> cause yet.
> > >>> For now, we've worked around this by disabling the readline module with 
> > >>> the
> > >>> attached patch.
> > >>>
> > >>> -Tom
> > >>>
> >  $ lldb
> >  (lldb) script
> >   #0 0x7f3d324c9c2a 
> >  llvm::sys::PrintStackTrace(llvm::raw_ostream&) 
> >  (/home/rjodin/work/dpu_tools3/build/lib/libLLVM-9.so+0x6bfc2a)
> >   #1 0x7f3d324c7af5 llvm::sys::RunSignalHandlers() 
> >  (/home/rjodin/work/dpu_tools3/build/lib/libLLVM-9.so+0x6bdaf5)
> >   #2 0x7f3d324c7c0c SignalHandler(int) 
> >  (/home/rjodin/work/dpu_tools3/build/lib/libLLVM-9.so+0x6bdc0c)
> >   #3 0x7f3d31bfe0e0 __restore_rt 
> >  (/lib/x86_64-linux-gnu/libpthread.so.0+0x110e0)
> >   #4 0x7f3d2d18f81b PyModule_GetState 
> >  (/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0x6881b)
> >   #5 0x7f3d230e1621 _init 
> >  (/usr/lib/python3.5/lib-dynload/readline.cpython-35m-x86_64-linux-gnu.so
> >   +0x3621)
> >   #6 0x7f3d2e3dece1 rl_initialize 
> >  (/usr/lib/x86_64-linux-gnu/libedit.so.2+0x1dce1)
> >   #7 0x7f3d230e1f3e _init 
> >  (/usr/lib/python3.5/lib-dynload/readline.cpython-35m-x86_64-linux-gnu.so
> >   +0x3f3e)
> >   #8 0x7f3d2d32d710 _PyImport_LoadDynamicModuleWithSpec 
> >  (/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0x206710)
> >   #9 0x7f3d2d330fe7 
> >  (/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0x209fe7)
> >  #10 0x7f3d2d198259 PyCFunction_Call 
> >  (/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0x71259)
> >  #11 0x7f3d2d2c8ff2 PyEval_EvalFrameEx 
> >  (/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0x1a1ff2)
> >  #12 0x7f3d2d38b074 
> >  (/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0x264074)
> >  #13 0x7f3d2d2c7adf PyEval_EvalFrameEx 
> >  (/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0x1a0adf)
> >  #14 0x7f3d2d2c96ad PyEval_EvalFrameEx 
> >  (/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0x1a26ad)
> >  #15 0x7f3d2d2c96ad PyEval_EvalFrameEx 
> >  (/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0x1a26ad)
> >  #16 0x7f3d2d2c96ad PyEval_EvalFrameEx 
> >  (/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0x1a26ad)
> >  #17 0x7f3d2d2c96ad PyEval_EvalFrameEx 
> >  (/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0x1a26ad)
> >

Re: [lldb-dev] issue with lldb9 and python3.5

2019-10-28 Thread Adrian McCarthy via lldb-dev 
+1 Yes, for Windows, I'd be happy if we said Python 3.6+.

On Mon, Oct 28, 2019 at 10:07 AM Jonas Devlieghere via lldb-dev <
lldb-dev@lists.llvm.org> wrote:

> On Mon, Oct 28, 2019 at 10:04 AM Jonas Devlieghere
>  wrote:
> >
> > On Mon, Oct 28, 2019 at 9:32 AM Tom Stellard 
> wrote:
> > >
> > > On 10/28/2019 09:29 AM, Jonas Devlieghere wrote:
> > > > Yes, Python 3.5 is not supported. We "officially" support Python 2.7
> > > > and Python 3.7. I'm sorry if we forgot that in the release notes.
> > > >
> > >
> > > Is there a specific reason why 3.5 is not supported?  Is it
> > > because of this issue?
> >
> > Not really other than the lack of testing/CI.
> >
> > - The Linux bots are all running with Python 2.7.
> > - I know that on macOS we ran into issues with some older versions. I
> > don't remember if it was this particular issue and I'm not even sure
> > if that was using Python 3.5 or Python 3.6. Our bots on GreenDragon
> > all run with Python 3.7.
> > - Stella's Windows bot is running Python 3.6 so we should consider
> > that supported as well.
>
> For completeness, Python 2.7 is not supported on Windows at all. The
> docs specify Python 3.5 or later. Maybe we should bump that to 3.6
> too?
>
> >
> > >
> > > -Tom
> > >
> > > > On Mon, Oct 28, 2019 at 7:06 AM Tom Stellard via lldb-dev
> > > >  wrote:
> > > >>
> > > >> + lldb-dev
> > > >>
> > > >> On 10/28/2019 07:06 AM, Tom Stellard wrote:
> > > >>> On 10/28/2019 03:50 AM, Romaric Jodin via lldb-dev wrote:
> > >  Hi everyone,
> > > 
> > >  I have lldb crashing since I've updated to lldb9. Seems like
> there is a issue with python3.5. Everything seems to work fine with
> python3.7.
> > >  Am I missing something? Or is it a known issue?
> > > 
> > > >>>
> > > >>> We have seen this too with python 3.6, but we haven't found the
> root cause yet.
> > > >>> For now, we've worked around this by disabling the readline module
> with the
> > > >>> attached patch.
> > > >>>
> > > >>> -Tom
> > > >>>
> > >  $ lldb
> > >  (lldb) script
> > >   #0 0x7f3d324c9c2a
> llvm::sys::PrintStackTrace(llvm::raw_ostream&)
> (/home/rjodin/work/dpu_tools3/build/lib/libLLVM-9.so+0x6bfc2a)
> > >   #1 0x7f3d324c7af5 llvm::sys::RunSignalHandlers()
> (/home/rjodin/work/dpu_tools3/build/lib/libLLVM-9.so+0x6bdaf5)
> > >   #2 0x7f3d324c7c0c SignalHandler(int)
> (/home/rjodin/work/dpu_tools3/build/lib/libLLVM-9.so+0x6bdc0c)
> > >   #3 0x7f3d31bfe0e0 __restore_rt
> (/lib/x86_64-linux-gnu/libpthread.so.0+0x110e0)
> > >   #4 0x7f3d2d18f81b PyModule_GetState
> (/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0x6881b)
> > >   #5 0x7f3d230e1621 _init (/usr/lib/python3.5/lib-dynload/
> readline.cpython-35m-x86_64-linux-gnu.so <
> http://readline.cpython-35m-x86_64-linux-gnu.so>+0x3621)
> > >   #6 0x7f3d2e3dece1 rl_initialize
> (/usr/lib/x86_64-linux-gnu/libedit.so.2+0x1dce1)
> > >   #7 0x7f3d230e1f3e _init (/usr/lib/python3.5/lib-dynload/
> readline.cpython-35m-x86_64-linux-gnu.so <
> http://readline.cpython-35m-x86_64-linux-gnu.so>+0x3f3e)
> > >   #8 0x7f3d2d32d710 _PyImport_LoadDynamicModuleWithSpec
> (/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0x206710)
> > >   #9 0x7f3d2d330fe7
> (/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0x209fe7)
> > >  #10 0x7f3d2d198259 PyCFunction_Call
> (/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0x71259)
> > >  #11 0x7f3d2d2c8ff2 PyEval_EvalFrameEx
> (/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0x1a1ff2)
> > >  #12 0x7f3d2d38b074
> (/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0x264074)
> > >  #13 0x7f3d2d2c7adf PyEval_EvalFrameEx
> (/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0x1a0adf)
> > >  #14 0x7f3d2d2c96ad PyEval_EvalFrameEx
> (/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0x1a26ad)
> > >  #15 0x7f3d2d2c96ad PyEval_EvalFrameEx
> (/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0x1a26ad)
> > >  #16 0x7f3d2d2c96ad PyEval_EvalFrameEx
> (/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0x1a26ad)
> > >  #17 0x7f3d2d2c96ad PyEval_EvalFrameEx
> (/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0x1a26ad)
> > >  #18 0x7f3d2d38b074
> (/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0x264074)
> > >  #19 0x7f3d2d38b153 PyEval_EvalCodeEx
> (/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0x264153)
> > >  #20 0x7f3d2d21e558
> (/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0xf7558)
> > >  #21 0x7f3d2d2faa37 PyObject_Call
> (/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0x1d3a37)
> > >  #22 0x7f3d2d2fce1b _PyObject_CallMethodIdObjArgs
> (/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0x1d5e1b)
> > >  #23 0x7f3d2d32effa PyImport_ImportModuleLevelObject
> (/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0x207ffa)
> > >  #24

Re: [lldb-dev] issue with lldb9 and python3.5

2019-10-28 Thread Jonas Devlieghere via lldb-dev 
On Mon, Oct 28, 2019 at 10:04 AM Jonas Devlieghere
 wrote:
>
> On Mon, Oct 28, 2019 at 9:32 AM Tom Stellard  wrote:
> >
> > On 10/28/2019 09:29 AM, Jonas Devlieghere wrote:
> > > Yes, Python 3.5 is not supported. We "officially" support Python 2.7
> > > and Python 3.7. I'm sorry if we forgot that in the release notes.
> > >
> >
> > Is there a specific reason why 3.5 is not supported?  Is it
> > because of this issue?
>
> Not really other than the lack of testing/CI.
>
> - The Linux bots are all running with Python 2.7.
> - I know that on macOS we ran into issues with some older versions. I
> don't remember if it was this particular issue and I'm not even sure
> if that was using Python 3.5 or Python 3.6. Our bots on GreenDragon
> all run with Python 3.7.
> - Stella's Windows bot is running Python 3.6 so we should consider
> that supported as well.

For completeness, Python 2.7 is not supported on Windows at all. The
docs specify Python 3.5 or later. Maybe we should bump that to 3.6
too?

>
> >
> > -Tom
> >
> > > On Mon, Oct 28, 2019 at 7:06 AM Tom Stellard via lldb-dev
> > >  wrote:
> > >>
> > >> + lldb-dev
> > >>
> > >> On 10/28/2019 07:06 AM, Tom Stellard wrote:
> > >>> On 10/28/2019 03:50 AM, Romaric Jodin via lldb-dev wrote:
> >  Hi everyone,
> > 
> >  I have lldb crashing since I've updated to lldb9. Seems like there is 
> >  a issue with python3.5. Everything seems to work fine with python3.7.
> >  Am I missing something? Or is it a known issue?
> > 
> > >>>
> > >>> We have seen this too with python 3.6, but we haven't found the root 
> > >>> cause yet.
> > >>> For now, we've worked around this by disabling the readline module with 
> > >>> the
> > >>> attached patch.
> > >>>
> > >>> -Tom
> > >>>
> >  $ lldb
> >  (lldb) script
> >   #0 0x7f3d324c9c2a 
> >  llvm::sys::PrintStackTrace(llvm::raw_ostream&) 
> >  (/home/rjodin/work/dpu_tools3/build/lib/libLLVM-9.so+0x6bfc2a)
> >   #1 0x7f3d324c7af5 llvm::sys::RunSignalHandlers() 
> >  (/home/rjodin/work/dpu_tools3/build/lib/libLLVM-9.so+0x6bdaf5)
> >   #2 0x7f3d324c7c0c SignalHandler(int) 
> >  (/home/rjodin/work/dpu_tools3/build/lib/libLLVM-9.so+0x6bdc0c)
> >   #3 0x7f3d31bfe0e0 __restore_rt 
> >  (/lib/x86_64-linux-gnu/libpthread.so.0+0x110e0)
> >   #4 0x7f3d2d18f81b PyModule_GetState 
> >  (/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0x6881b)
> >   #5 0x7f3d230e1621 _init 
> >  (/usr/lib/python3.5/lib-dynload/readline.cpython-35m-x86_64-linux-gnu.so
> >   +0x3621)
> >   #6 0x7f3d2e3dece1 rl_initialize 
> >  (/usr/lib/x86_64-linux-gnu/libedit.so.2+0x1dce1)
> >   #7 0x7f3d230e1f3e _init 
> >  (/usr/lib/python3.5/lib-dynload/readline.cpython-35m-x86_64-linux-gnu.so
> >   +0x3f3e)
> >   #8 0x7f3d2d32d710 _PyImport_LoadDynamicModuleWithSpec 
> >  (/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0x206710)
> >   #9 0x7f3d2d330fe7 
> >  (/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0x209fe7)
> >  #10 0x7f3d2d198259 PyCFunction_Call 
> >  (/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0x71259)
> >  #11 0x7f3d2d2c8ff2 PyEval_EvalFrameEx 
> >  (/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0x1a1ff2)
> >  #12 0x7f3d2d38b074 
> >  (/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0x264074)
> >  #13 0x7f3d2d2c7adf PyEval_EvalFrameEx 
> >  (/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0x1a0adf)
> >  #14 0x7f3d2d2c96ad PyEval_EvalFrameEx 
> >  (/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0x1a26ad)
> >  #15 0x7f3d2d2c96ad PyEval_EvalFrameEx 
> >  (/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0x1a26ad)
> >  #16 0x7f3d2d2c96ad PyEval_EvalFrameEx 
> >  (/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0x1a26ad)
> >  #17 0x7f3d2d2c96ad PyEval_EvalFrameEx 
> >  (/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0x1a26ad)
> >  #18 0x7f3d2d38b074 
> >  (/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0x264074)
> >  #19 0x7f3d2d38b153 PyEval_EvalCodeEx 
> >  (/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0x264153)
> >  #20 0x7f3d2d21e558 
> >  (/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0xf7558)
> >  #21 0x7f3d2d2faa37 PyObject_Call 
> >  (/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0x1d3a37)
> >  #22 0x7f3d2d2fce1b _PyObject_CallMethodIdObjArgs 
> >  (/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0x1d5e1b)
> >  #23 0x7f3d2d32effa PyImport_ImportModuleLevelObject 
> >  (/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0x207ffa)
> >  #24 0x7f3d2d2cd248 
> >  (/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0x1a6248)
> >

Re: [lldb-dev] issue with lldb9 and python3.5

2019-10-28 Thread Jonas Devlieghere via lldb-dev 
On Mon, Oct 28, 2019 at 9:32 AM Tom Stellard  wrote:
>
> On 10/28/2019 09:29 AM, Jonas Devlieghere wrote:
> > Yes, Python 3.5 is not supported. We "officially" support Python 2.7
> > and Python 3.7. I'm sorry if we forgot that in the release notes.
> >
>
> Is there a specific reason why 3.5 is not supported?  Is it
> because of this issue?

Not really other than the lack of testing/CI.

- The Linux bots are all running with Python 2.7.
- I know that on macOS we ran into issues with some older versions. I
don't remember if it was this particular issue and I'm not even sure
if that was using Python 3.5 or Python 3.6. Our bots on GreenDragon
all run with Python 3.7.
- Stella's Windows bot is running Python 3.6 so we should consider
that supported as well.

>
> -Tom
>
> > On Mon, Oct 28, 2019 at 7:06 AM Tom Stellard via lldb-dev
> >  wrote:
> >>
> >> + lldb-dev
> >>
> >> On 10/28/2019 07:06 AM, Tom Stellard wrote:
> >>> On 10/28/2019 03:50 AM, Romaric Jodin via lldb-dev wrote:
>  Hi everyone,
> 
>  I have lldb crashing since I've updated to lldb9. Seems like there is a 
>  issue with python3.5. Everything seems to work fine with python3.7.
>  Am I missing something? Or is it a known issue?
> 
> >>>
> >>> We have seen this too with python 3.6, but we haven't found the root 
> >>> cause yet.
> >>> For now, we've worked around this by disabling the readline module with 
> >>> the
> >>> attached patch.
> >>>
> >>> -Tom
> >>>
>  $ lldb
>  (lldb) script
>   #0 0x7f3d324c9c2a 
>  llvm::sys::PrintStackTrace(llvm::raw_ostream&) 
>  (/home/rjodin/work/dpu_tools3/build/lib/libLLVM-9.so+0x6bfc2a)
>   #1 0x7f3d324c7af5 llvm::sys::RunSignalHandlers() 
>  (/home/rjodin/work/dpu_tools3/build/lib/libLLVM-9.so+0x6bdaf5)
>   #2 0x7f3d324c7c0c SignalHandler(int) 
>  (/home/rjodin/work/dpu_tools3/build/lib/libLLVM-9.so+0x6bdc0c)
>   #3 0x7f3d31bfe0e0 __restore_rt 
>  (/lib/x86_64-linux-gnu/libpthread.so.0+0x110e0)
>   #4 0x7f3d2d18f81b PyModule_GetState 
>  (/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0x6881b)
>   #5 0x7f3d230e1621 _init 
>  (/usr/lib/python3.5/lib-dynload/readline.cpython-35m-x86_64-linux-gnu.so 
>  +0x3621)
>   #6 0x7f3d2e3dece1 rl_initialize 
>  (/usr/lib/x86_64-linux-gnu/libedit.so.2+0x1dce1)
>   #7 0x7f3d230e1f3e _init 
>  (/usr/lib/python3.5/lib-dynload/readline.cpython-35m-x86_64-linux-gnu.so 
>  +0x3f3e)
>   #8 0x7f3d2d32d710 _PyImport_LoadDynamicModuleWithSpec 
>  (/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0x206710)
>   #9 0x7f3d2d330fe7 
>  (/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0x209fe7)
>  #10 0x7f3d2d198259 PyCFunction_Call 
>  (/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0x71259)
>  #11 0x7f3d2d2c8ff2 PyEval_EvalFrameEx 
>  (/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0x1a1ff2)
>  #12 0x7f3d2d38b074 
>  (/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0x264074)
>  #13 0x7f3d2d2c7adf PyEval_EvalFrameEx 
>  (/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0x1a0adf)
>  #14 0x7f3d2d2c96ad PyEval_EvalFrameEx 
>  (/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0x1a26ad)
>  #15 0x7f3d2d2c96ad PyEval_EvalFrameEx 
>  (/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0x1a26ad)
>  #16 0x7f3d2d2c96ad PyEval_EvalFrameEx 
>  (/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0x1a26ad)
>  #17 0x7f3d2d2c96ad PyEval_EvalFrameEx 
>  (/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0x1a26ad)
>  #18 0x7f3d2d38b074 
>  (/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0x264074)
>  #19 0x7f3d2d38b153 PyEval_EvalCodeEx 
>  (/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0x264153)
>  #20 0x7f3d2d21e558 
>  (/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0xf7558)
>  #21 0x7f3d2d2faa37 PyObject_Call 
>  (/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0x1d3a37)
>  #22 0x7f3d2d2fce1b _PyObject_CallMethodIdObjArgs 
>  (/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0x1d5e1b)
>  #23 0x7f3d2d32effa PyImport_ImportModuleLevelObject 
>  (/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0x207ffa)
>  #24 0x7f3d2d2cd248 
>  (/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0x1a6248)
>  #25 0x7f3d2d198279 PyCFunction_Call 
>  (/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0x71279)
>  #26 0x7f3d2d2faa37 PyObject_Call 
>  (/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0x1d3a37)
>  #27 0x7f3d2d389b77 PyEval_CallObjectWithKeywords 
>  (/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0x262b77)
>  #28 0x7f3d2d2c57cb

[lldb-dev] [Bug 43830] lldb crashes when loading Python 3.6 interpreter

2019-10-28 Thread via lldb-dev 
https://bugs.llvm.org/show_bug.cgi?id=43830

sguel...@redhat.com changed:

   What|Removed |Added

   Assignee|lldb-dev@lists.llvm.org |sguel...@redhat.com

-- 
You are receiving this mail because:
You are the assignee for the bug.___
lldb-dev mailing list
lldb-dev@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev

[lldb-dev] [Bug 43830] New: lldb crashes when loading Python 3.6 interpreter

2019-10-28 Thread via lldb-dev 
https://bugs.llvm.org/show_bug.cgi?id=43830

Bug ID: 43830
   Summary: lldb crashes when loading Python 3.6 interpreter
   Product: lldb
   Version: 9.0
  Hardware: PC
OS: Linux
Status: NEW
  Severity: enhancement
  Priority: P
 Component: All Bugs
  Assignee: lldb-dev@lists.llvm.org
  Reporter: sguel...@redhat.com
CC: jdevliegh...@apple.com, llvm-b...@lists.llvm.org

Reproducer:

$ lldb -o script
(lldb) script
 #0 0x7f89c6b890ee llvm::sys::PrintStackTrace(llvm::raw_ostream&)
/home/sguelton/sources/llvm-project/llvm/lib/Support/Unix/Signals.inc:533:22
 #1 0x7f89c6b89181 PrintStackTraceSignalHandler(void*)
/home/sguelton/sources/llvm-project/llvm/lib/Support/Unix/Signals.inc:594:1
 #2 0x7f89c6b87323 llvm::sys::RunSignalHandlers()
/home/sguelton/sources/llvm-project/llvm/lib/Support/Signals.cpp:68:20
 #3 0x7f89c6b88b6a SignalHandler(int)
/home/sguelton/sources/llvm-project/llvm/lib/Support/Unix/Signals.inc:385:1
 #4 0x7f89c65d3680 __restore_rt (/lib64/libpthread.so.0+0xf680)
 #5 0x7f89c0fd5cf4 PyModule_GetState
(/opt/rh/rh-python36/root/usr/lib64/libpython3.6m.so.rh-python36-1.0+0xe3cf4)
 #6 0x7f89a36e0ed9 _init
(/opt/rh/rh-python36/root/usr/lib64/python3.6/lib-dynload/readline.cpython-36m-x86_64-linux-gnu.so+0x3ed9)
 #7 0x7f89b79acff5 rl_initialize (/lib64/libedit.so.0+0x20ff5)
 #8 0x7f89a36e168f PyInit_readline
(/opt/rh/rh-python36/root/usr/lib64/python3.6/lib-dynload/readline.cpython-36m-x86_64-linux-gnu.so+0x468f)
 #9 0x7f89c10c842f _PyImport_LoadDynamicModuleWithSpec
(/opt/rh/rh-python36/root/usr/lib64/libpython3.6m.so.rh-python36-1.0+0x1d642f)
#10 0x7f89c10c7ca4
(/opt/rh/rh-python36/root/usr/lib64/libpython3.6m.so.rh-python36-1.0+0x1d5ca4)
#11 0x7f89c0fd55f7 PyCFunction_Call
(/opt/rh/rh-python36/root/usr/lib64/libpython3.6m.so.rh-python36-1.0+0xe35f7)
#12 0x7f89c103c9b2 _PyEval_EvalFrameDefault
(/opt/rh/rh-python36/root/usr/lib64/libpython3.6m.so.rh-python36-1.0+0x14a9b2)
#13 0x7f89c1040c8c
(/opt/rh/rh-python36/root/usr/lib64/libpython3.6m.so.rh-python36-1.0+0x14ec8c)
#14 0x7f89c1041aba
(/opt/rh/rh-python36/root/usr/lib64/libpython3.6m.so.rh-python36-1.0+0x14faba)
#15 0x7f89c1041e23
(/opt/rh/rh-python36/root/usr/lib64/libpython3.6m.so.rh-python36-1.0+0x14fe23)
#16 0x7f89c10362a7 _PyEval_EvalFrameDefault
(/opt/rh/rh-python36/root/usr/lib64/libpython3.6m.so.rh-python36-1.0+0x1442a7)
#17 0x7f89c1041a0a
(/opt/rh/rh-python36/root/usr/lib64/libpython3.6m.so.rh-python36-1.0+0x14fa0a)
#18 0x7f89c1041e23
(/opt/rh/rh-python36/root/usr/lib64/libpython3.6m.so.rh-python36-1.0+0x14fe23)
#19 0x7f89c10362a7 _PyEval_EvalFrameDefault
(/opt/rh/rh-python36/root/usr/lib64/libpython3.6m.so.rh-python36-1.0+0x1442a7)
#20 0x7f89c1041a0a
(/opt/rh/rh-python36/root/usr/lib64/libpython3.6m.so.rh-python36-1.0+0x14fa0a)
#21 0x7f89c1041e23
(/opt/rh/rh-python36/root/usr/lib64/libpython3.6m.so.rh-python36-1.0+0x14fe23)
#22 0x7f89c10362a7 _PyEval_EvalFrameDefault
(/opt/rh/rh-python36/root/usr/lib64/libpython3.6m.so.rh-python36-1.0+0x1442a7)
#23 0x7f89c1041a0a
(/opt/rh/rh-python36/root/usr/lib64/libpython3.6m.so.rh-python36-1.0+0x14fa0a)
#24 0x7f89c1041e23
(/opt/rh/rh-python36/root/usr/lib64/libpython3.6m.so.rh-python36-1.0+0x14fe23)
#25 0x7f89c10362a7 _PyEval_EvalFrameDefault
(/opt/rh/rh-python36/root/usr/lib64/libpython3.6m.so.rh-python36-1.0+0x1442a7)
#26 0x7f89c1041a0a
(/opt/rh/rh-python36/root/usr/lib64/libpython3.6m.so.rh-python36-1.0+0x14fa0a)
#27 0x7f89c1041e23
(/opt/rh/rh-python36/root/usr/lib64/libpython3.6m.so.rh-python36-1.0+0x14fe23)
#28 0x7f89c10362a7 _PyEval_EvalFrameDefault
(/opt/rh/rh-python36/root/usr/lib64/libpython3.6m.so.rh-python36-1.0+0x1442a7)
#29 0x7f89c1042f12 _PyFunction_FastCallDict
(/opt/rh/rh-python36/root/usr/lib64/libpython3.6m.so.rh-python36-1.0+0x150f12)
#30 0x7f89c0f980ce _PyObject_FastCallDict
(/opt/rh/rh-python36/root/usr/lib64/libpython3.6m.so.rh-python36-1.0+0xa60ce)
#31 0x7f89c0f993f4 _PyObject_CallMethodIdObjArgs
(/opt/rh/rh-python36/root/usr/lib64/libpython3.6m.so.rh-python36-1.0+0xa73f4)
#32 0x7f89c105a28f PyImport_ImportModuleLevelObject
(/opt/rh/rh-python36/root/usr/lib64/libpython3.6m.so.rh-python36-1.0+0x16828f)
#33 0x7f89c1039201 _PyEval_EvalFrameDefault
(/opt/rh/rh-python36/root/usr/lib64/libpython3.6m.so.rh-python36-1.0+0x147201)
#34 0x7f89c1042122 PyEval_EvalCodeEx
(/opt/rh/rh-python36/root/usr/lib64/libpython3.6m.so.rh-python36-1.0+0x150122)
#35 0x7f89c1042dbb PyEval_EvalCode
(/opt/rh/rh-python36/root/usr/lib64/libpython3.6m.so.rh-python36-1.0+0x150dbb)
#36 0x7f89c10352cb
(/opt/rh/rh-python36/root/usr/lib64/libpython3.6m.so.rh-python36-1.0+0x1432cb)
#37 0x7f89c0fd55f7 PyCFunction_Call
(/opt/rh/rh-python36/root/usr/lib64/libpython3.6m.so.rh-python36-1.0+0xe35f7)
#38 0x7f89c103c9b2 _PyEval_EvalFrameDefault

Re: [lldb-dev] issue with lldb9 and python3.5

2019-10-28 Thread Tom Stellard via lldb-dev 
On 10/28/2019 09:29 AM, Jonas Devlieghere wrote:
> Yes, Python 3.5 is not supported. We "officially" support Python 2.7
> and Python 3.7. I'm sorry if we forgot that in the release notes.
> 

Is there a specific reason why 3.5 is not supported?  Is it
because of this issue?

-Tom

> On Mon, Oct 28, 2019 at 7:06 AM Tom Stellard via lldb-dev
>  wrote:
>>
>> + lldb-dev
>>
>> On 10/28/2019 07:06 AM, Tom Stellard wrote:
>>> On 10/28/2019 03:50 AM, Romaric Jodin via lldb-dev wrote:
 Hi everyone,

 I have lldb crashing since I've updated to lldb9. Seems like there is a 
 issue with python3.5. Everything seems to work fine with python3.7.
 Am I missing something? Or is it a known issue?

>>>
>>> We have seen this too with python 3.6, but we haven't found the root cause 
>>> yet.
>>> For now, we've worked around this by disabling the readline module with the
>>> attached patch.
>>>
>>> -Tom
>>>
 $ lldb
 (lldb) script
  #0 0x7f3d324c9c2a llvm::sys::PrintStackTrace(llvm::raw_ostream&) 
 (/home/rjodin/work/dpu_tools3/build/lib/libLLVM-9.so+0x6bfc2a)
  #1 0x7f3d324c7af5 llvm::sys::RunSignalHandlers() 
 (/home/rjodin/work/dpu_tools3/build/lib/libLLVM-9.so+0x6bdaf5)
  #2 0x7f3d324c7c0c SignalHandler(int) 
 (/home/rjodin/work/dpu_tools3/build/lib/libLLVM-9.so+0x6bdc0c)
  #3 0x7f3d31bfe0e0 __restore_rt 
 (/lib/x86_64-linux-gnu/libpthread.so.0+0x110e0)
  #4 0x7f3d2d18f81b PyModule_GetState 
 (/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0x6881b)
  #5 0x7f3d230e1621 _init 
 (/usr/lib/python3.5/lib-dynload/readline.cpython-35m-x86_64-linux-gnu.so 
 +0x3621)
  #6 0x7f3d2e3dece1 rl_initialize 
 (/usr/lib/x86_64-linux-gnu/libedit.so.2+0x1dce1)
  #7 0x7f3d230e1f3e _init 
 (/usr/lib/python3.5/lib-dynload/readline.cpython-35m-x86_64-linux-gnu.so 
 +0x3f3e)
  #8 0x7f3d2d32d710 _PyImport_LoadDynamicModuleWithSpec 
 (/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0x206710)
  #9 0x7f3d2d330fe7 
 (/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0x209fe7)
 #10 0x7f3d2d198259 PyCFunction_Call 
 (/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0x71259)
 #11 0x7f3d2d2c8ff2 PyEval_EvalFrameEx 
 (/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0x1a1ff2)
 #12 0x7f3d2d38b074 
 (/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0x264074)
 #13 0x7f3d2d2c7adf PyEval_EvalFrameEx 
 (/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0x1a0adf)
 #14 0x7f3d2d2c96ad PyEval_EvalFrameEx 
 (/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0x1a26ad)
 #15 0x7f3d2d2c96ad PyEval_EvalFrameEx 
 (/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0x1a26ad)
 #16 0x7f3d2d2c96ad PyEval_EvalFrameEx 
 (/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0x1a26ad)
 #17 0x7f3d2d2c96ad PyEval_EvalFrameEx 
 (/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0x1a26ad)
 #18 0x7f3d2d38b074 
 (/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0x264074)
 #19 0x7f3d2d38b153 PyEval_EvalCodeEx 
 (/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0x264153)
 #20 0x7f3d2d21e558 
 (/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0xf7558)
 #21 0x7f3d2d2faa37 PyObject_Call 
 (/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0x1d3a37)
 #22 0x7f3d2d2fce1b _PyObject_CallMethodIdObjArgs 
 (/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0x1d5e1b)
 #23 0x7f3d2d32effa PyImport_ImportModuleLevelObject 
 (/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0x207ffa)
 #24 0x7f3d2d2cd248 
 (/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0x1a6248)
 #25 0x7f3d2d198279 PyCFunction_Call 
 (/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0x71279)
 #26 0x7f3d2d2faa37 PyObject_Call 
 (/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0x1d3a37)
 #27 0x7f3d2d389b77 PyEval_CallObjectWithKeywords 
 (/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0x262b77)
 #28 0x7f3d2d2c57cb PyEval_EvalFrameEx 
 (/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0x19e7cb)
 #29 0x7f3d2d38b074 
 (/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0x264074)
 #30 0x7f3d2d38b153 PyEval_EvalCodeEx 
 (/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0x264153)
 #31 0x7f3d2d2c145b PyEval_EvalCode 
 (/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0x19a45b)
 #32 0x7f3d2d2ce2cd 
 (/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0x1a72cd)
 #33 0x7f3d2d198259 PyCFunction_Call 
 (/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0x71259)
 #34 0x7f3d2d2c8ff2 PyEval_EvalFrameEx

Re: [lldb-dev] issue with lldb9 and python3.5

2019-10-28 Thread Jonas Devlieghere via lldb-dev 
Yes, Python 3.5 is not supported. We "officially" support Python 2.7
and Python 3.7. I'm sorry if we forgot that in the release notes.

On Mon, Oct 28, 2019 at 7:06 AM Tom Stellard via lldb-dev
 wrote:
>
> + lldb-dev
>
> On 10/28/2019 07:06 AM, Tom Stellard wrote:
> > On 10/28/2019 03:50 AM, Romaric Jodin via lldb-dev wrote:
> >> Hi everyone,
> >>
> >> I have lldb crashing since I've updated to lldb9. Seems like there is a 
> >> issue with python3.5. Everything seems to work fine with python3.7.
> >> Am I missing something? Or is it a known issue?
> >>
> >
> > We have seen this too with python 3.6, but we haven't found the root cause 
> > yet.
> > For now, we've worked around this by disabling the readline module with the
> > attached patch.
> >
> > -Tom
> >
> >> $ lldb
> >> (lldb) script
> >>  #0 0x7f3d324c9c2a llvm::sys::PrintStackTrace(llvm::raw_ostream&) 
> >> (/home/rjodin/work/dpu_tools3/build/lib/libLLVM-9.so+0x6bfc2a)
> >>  #1 0x7f3d324c7af5 llvm::sys::RunSignalHandlers() 
> >> (/home/rjodin/work/dpu_tools3/build/lib/libLLVM-9.so+0x6bdaf5)
> >>  #2 0x7f3d324c7c0c SignalHandler(int) 
> >> (/home/rjodin/work/dpu_tools3/build/lib/libLLVM-9.so+0x6bdc0c)
> >>  #3 0x7f3d31bfe0e0 __restore_rt 
> >> (/lib/x86_64-linux-gnu/libpthread.so.0+0x110e0)
> >>  #4 0x7f3d2d18f81b PyModule_GetState 
> >> (/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0x6881b)
> >>  #5 0x7f3d230e1621 _init 
> >> (/usr/lib/python3.5/lib-dynload/readline.cpython-35m-x86_64-linux-gnu.so 
> >> +0x3621)
> >>  #6 0x7f3d2e3dece1 rl_initialize 
> >> (/usr/lib/x86_64-linux-gnu/libedit.so.2+0x1dce1)
> >>  #7 0x7f3d230e1f3e _init 
> >> (/usr/lib/python3.5/lib-dynload/readline.cpython-35m-x86_64-linux-gnu.so 
> >> +0x3f3e)
> >>  #8 0x7f3d2d32d710 _PyImport_LoadDynamicModuleWithSpec 
> >> (/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0x206710)
> >>  #9 0x7f3d2d330fe7 
> >> (/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0x209fe7)
> >> #10 0x7f3d2d198259 PyCFunction_Call 
> >> (/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0x71259)
> >> #11 0x7f3d2d2c8ff2 PyEval_EvalFrameEx 
> >> (/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0x1a1ff2)
> >> #12 0x7f3d2d38b074 
> >> (/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0x264074)
> >> #13 0x7f3d2d2c7adf PyEval_EvalFrameEx 
> >> (/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0x1a0adf)
> >> #14 0x7f3d2d2c96ad PyEval_EvalFrameEx 
> >> (/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0x1a26ad)
> >> #15 0x7f3d2d2c96ad PyEval_EvalFrameEx 
> >> (/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0x1a26ad)
> >> #16 0x7f3d2d2c96ad PyEval_EvalFrameEx 
> >> (/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0x1a26ad)
> >> #17 0x7f3d2d2c96ad PyEval_EvalFrameEx 
> >> (/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0x1a26ad)
> >> #18 0x7f3d2d38b074 
> >> (/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0x264074)
> >> #19 0x7f3d2d38b153 PyEval_EvalCodeEx 
> >> (/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0x264153)
> >> #20 0x7f3d2d21e558 
> >> (/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0xf7558)
> >> #21 0x7f3d2d2faa37 PyObject_Call 
> >> (/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0x1d3a37)
> >> #22 0x7f3d2d2fce1b _PyObject_CallMethodIdObjArgs 
> >> (/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0x1d5e1b)
> >> #23 0x7f3d2d32effa PyImport_ImportModuleLevelObject 
> >> (/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0x207ffa)
> >> #24 0x7f3d2d2cd248 
> >> (/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0x1a6248)
> >> #25 0x7f3d2d198279 PyCFunction_Call 
> >> (/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0x71279)
> >> #26 0x7f3d2d2faa37 PyObject_Call 
> >> (/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0x1d3a37)
> >> #27 0x7f3d2d389b77 PyEval_CallObjectWithKeywords 
> >> (/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0x262b77)
> >> #28 0x7f3d2d2c57cb PyEval_EvalFrameEx 
> >> (/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0x19e7cb)
> >> #29 0x7f3d2d38b074 
> >> (/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0x264074)
> >> #30 0x7f3d2d38b153 PyEval_EvalCodeEx 
> >> (/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0x264153)
> >> #31 0x7f3d2d2c145b PyEval_EvalCode 
> >> (/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0x19a45b)
> >> #32 0x7f3d2d2ce2cd 
> >> (/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0x1a72cd)
> >> #33 0x7f3d2d198259 PyCFunction_Call 
> >> (/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0x71259)
> >> #34 0x7f3d2d2c8ff2 PyEval_EvalFrameEx 
> >> (/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0x1a1ff2)
> >> #35 0x7f3d2d38b074 
> >> (/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0x264074)
> >> #36

Re: [lldb-dev] issue with lldb9 and python3.5

2019-10-28 Thread Tom Stellard via lldb-dev 
+ lldb-dev

On 10/28/2019 07:06 AM, Tom Stellard wrote:
> On 10/28/2019 03:50 AM, Romaric Jodin via lldb-dev wrote:
>> Hi everyone,
>>
>> I have lldb crashing since I've updated to lldb9. Seems like there is a 
>> issue with python3.5. Everything seems to work fine with python3.7.
>> Am I missing something? Or is it a known issue?
>>
> 
> We have seen this too with python 3.6, but we haven't found the root cause 
> yet.
> For now, we've worked around this by disabling the readline module with the
> attached patch.
> 
> -Tom
> 
>> $ lldb
>> (lldb) script
>>  #0 0x7f3d324c9c2a llvm::sys::PrintStackTrace(llvm::raw_ostream&) 
>> (/home/rjodin/work/dpu_tools3/build/lib/libLLVM-9.so+0x6bfc2a)
>>  #1 0x7f3d324c7af5 llvm::sys::RunSignalHandlers() 
>> (/home/rjodin/work/dpu_tools3/build/lib/libLLVM-9.so+0x6bdaf5)
>>  #2 0x7f3d324c7c0c SignalHandler(int) 
>> (/home/rjodin/work/dpu_tools3/build/lib/libLLVM-9.so+0x6bdc0c)
>>  #3 0x7f3d31bfe0e0 __restore_rt 
>> (/lib/x86_64-linux-gnu/libpthread.so.0+0x110e0)
>>  #4 0x7f3d2d18f81b PyModule_GetState 
>> (/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0x6881b)
>>  #5 0x7f3d230e1621 _init 
>> (/usr/lib/python3.5/lib-dynload/readline.cpython-35m-x86_64-linux-gnu.so 
>> +0x3621)
>>  #6 0x7f3d2e3dece1 rl_initialize 
>> (/usr/lib/x86_64-linux-gnu/libedit.so.2+0x1dce1)
>>  #7 0x7f3d230e1f3e _init 
>> (/usr/lib/python3.5/lib-dynload/readline.cpython-35m-x86_64-linux-gnu.so 
>> +0x3f3e)
>>  #8 0x7f3d2d32d710 _PyImport_LoadDynamicModuleWithSpec 
>> (/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0x206710)
>>  #9 0x7f3d2d330fe7 
>> (/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0x209fe7)
>> #10 0x7f3d2d198259 PyCFunction_Call 
>> (/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0x71259)
>> #11 0x7f3d2d2c8ff2 PyEval_EvalFrameEx 
>> (/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0x1a1ff2)
>> #12 0x7f3d2d38b074 
>> (/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0x264074)
>> #13 0x7f3d2d2c7adf PyEval_EvalFrameEx 
>> (/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0x1a0adf)
>> #14 0x7f3d2d2c96ad PyEval_EvalFrameEx 
>> (/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0x1a26ad)
>> #15 0x7f3d2d2c96ad PyEval_EvalFrameEx 
>> (/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0x1a26ad)
>> #16 0x7f3d2d2c96ad PyEval_EvalFrameEx 
>> (/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0x1a26ad)
>> #17 0x7f3d2d2c96ad PyEval_EvalFrameEx 
>> (/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0x1a26ad)
>> #18 0x7f3d2d38b074 
>> (/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0x264074)
>> #19 0x7f3d2d38b153 PyEval_EvalCodeEx 
>> (/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0x264153)
>> #20 0x7f3d2d21e558 
>> (/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0xf7558)
>> #21 0x7f3d2d2faa37 PyObject_Call 
>> (/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0x1d3a37)
>> #22 0x7f3d2d2fce1b _PyObject_CallMethodIdObjArgs 
>> (/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0x1d5e1b)
>> #23 0x7f3d2d32effa PyImport_ImportModuleLevelObject 
>> (/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0x207ffa)
>> #24 0x7f3d2d2cd248 
>> (/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0x1a6248)
>> #25 0x7f3d2d198279 PyCFunction_Call 
>> (/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0x71279)
>> #26 0x7f3d2d2faa37 PyObject_Call 
>> (/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0x1d3a37)
>> #27 0x7f3d2d389b77 PyEval_CallObjectWithKeywords 
>> (/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0x262b77)
>> #28 0x7f3d2d2c57cb PyEval_EvalFrameEx 
>> (/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0x19e7cb)
>> #29 0x7f3d2d38b074 
>> (/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0x264074)
>> #30 0x7f3d2d38b153 PyEval_EvalCodeEx 
>> (/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0x264153)
>> #31 0x7f3d2d2c145b PyEval_EvalCode 
>> (/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0x19a45b)
>> #32 0x7f3d2d2ce2cd 
>> (/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0x1a72cd)
>> #33 0x7f3d2d198259 PyCFunction_Call 
>> (/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0x71259)
>> #34 0x7f3d2d2c8ff2 PyEval_EvalFrameEx 
>> (/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0x1a1ff2)
>> #35 0x7f3d2d38b074 
>> (/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0x264074)
>> #36 0x7f3d2d2c7adf PyEval_EvalFrameEx 
>> (/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0x1a0adf)
>> #37 0x7f3d2d2c96ad PyEval_EvalFrameEx 
>> (/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0x1a26ad)
>> #38 0x7f3d2d2c96ad PyEval_EvalFrameEx 
>> (/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0x1a26ad)
>> #39 0x7f3d2d2c96ad PyEval_EvalFrameEx 
>>

[lldb-dev] issue with lldb9 and python3.5

2019-10-28 Thread Romaric Jodin via lldb-dev 
Hi everyone,

I have lldb crashing since I've updated to lldb9. Seems like there is a
issue with python3.5. Everything seems to work fine with python3.7.
Am I missing something? Or is it a known issue?

$ lldb
(lldb) script
 #0 0x7f3d324c9c2a llvm::sys::PrintStackTrace(llvm::raw_ostream&)
(/home/rjodin/work/dpu_tools3/build/lib/libLLVM-9.so+0x6bfc2a)
 #1 0x7f3d324c7af5 llvm::sys::RunSignalHandlers()
(/home/rjodin/work/dpu_tools3/build/lib/libLLVM-9.so+0x6bdaf5)
 #2 0x7f3d324c7c0c SignalHandler(int)
(/home/rjodin/work/dpu_tools3/build/lib/libLLVM-9.so+0x6bdc0c)
 #3 0x7f3d31bfe0e0 __restore_rt
(/lib/x86_64-linux-gnu/libpthread.so.0+0x110e0)
 #4 0x7f3d2d18f81b PyModule_GetState
(/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0x6881b)
 #5 0x7f3d230e1621 _init (/usr/lib/python3.5/lib-dynload/
readline.cpython-35m-x86_64-linux-gnu.so+0x3621)
 #6 0x7f3d2e3dece1 rl_initialize
(/usr/lib/x86_64-linux-gnu/libedit.so.2+0x1dce1)
 #7 0x7f3d230e1f3e _init (/usr/lib/python3.5/lib-dynload/
readline.cpython-35m-x86_64-linux-gnu.so+0x3f3e)
 #8 0x7f3d2d32d710 _PyImport_LoadDynamicModuleWithSpec
(/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0x206710)
 #9 0x7f3d2d330fe7
(/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0x209fe7)
#10 0x7f3d2d198259 PyCFunction_Call
(/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0x71259)
#11 0x7f3d2d2c8ff2 PyEval_EvalFrameEx
(/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0x1a1ff2)
#12 0x7f3d2d38b074
(/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0x264074)
#13 0x7f3d2d2c7adf PyEval_EvalFrameEx
(/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0x1a0adf)
#14 0x7f3d2d2c96ad PyEval_EvalFrameEx
(/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0x1a26ad)
#15 0x7f3d2d2c96ad PyEval_EvalFrameEx
(/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0x1a26ad)
#16 0x7f3d2d2c96ad PyEval_EvalFrameEx
(/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0x1a26ad)
#17 0x7f3d2d2c96ad PyEval_EvalFrameEx
(/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0x1a26ad)
#18 0x7f3d2d38b074
(/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0x264074)
#19 0x7f3d2d38b153 PyEval_EvalCodeEx
(/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0x264153)
#20 0x7f3d2d21e558
(/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0xf7558)
#21 0x7f3d2d2faa37 PyObject_Call
(/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0x1d3a37)
#22 0x7f3d2d2fce1b _PyObject_CallMethodIdObjArgs
(/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0x1d5e1b)
#23 0x7f3d2d32effa PyImport_ImportModuleLevelObject
(/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0x207ffa)
#24 0x7f3d2d2cd248
(/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0x1a6248)
#25 0x7f3d2d198279 PyCFunction_Call
(/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0x71279)
#26 0x7f3d2d2faa37 PyObject_Call
(/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0x1d3a37)
#27 0x7f3d2d389b77 PyEval_CallObjectWithKeywords
(/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0x262b77)
#28 0x7f3d2d2c57cb PyEval_EvalFrameEx
(/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0x19e7cb)
#29 0x7f3d2d38b074
(/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0x264074)
#30 0x7f3d2d38b153 PyEval_EvalCodeEx
(/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0x264153)
#31 0x7f3d2d2c145b PyEval_EvalCode
(/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0x19a45b)
#32 0x7f3d2d2ce2cd
(/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0x1a72cd)
#33 0x7f3d2d198259 PyCFunction_Call
(/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0x71259)
#34 0x7f3d2d2c8ff2 PyEval_EvalFrameEx
(/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0x1a1ff2)
#35 0x7f3d2d38b074
(/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0x264074)
#36 0x7f3d2d2c7adf PyEval_EvalFrameEx
(/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0x1a0adf)
#37 0x7f3d2d2c96ad PyEval_EvalFrameEx
(/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0x1a26ad)
#38 0x7f3d2d2c96ad PyEval_EvalFrameEx
(/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0x1a26ad)
#39 0x7f3d2d2c96ad PyEval_EvalFrameEx
(/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0x1a26ad)
#40 0x7f3d2d38b074
(/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0x264074)
#41 0x7f3d2d38b153 PyEval_EvalCodeEx
(/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0x264153)
#42 0x7f3d2d21e558
(/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0xf7558)
#43 0x7f3d2d2faa37 PyObject_Call
(/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0x1d3a37)
#44 0x7f3d2d2fce1b _PyObject_CallMethodIdObjArgs
(/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0x1d5e1b)
#45 0x7f3d2d32effa PyImport_ImportModuleLevelObject
(/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0x207ffa)
#46 0x7f3d2d2cd248
(/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0x1a6248)
#47 0x7f3d2d198279 PyCFunction_Call
(/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0x71279)
#48 0x7f3d2d2faa37 PyObject_Call
(/usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0+0x1d3a37)