Re: [lldb-dev] RFC: Moving debug info parsing out of process

2019-02-26 Thread via lldb-dev
When I see this "parsing DWARF and turning it into something else" it is very reminiscent of what clayborg is trying to do with GSYM. You're both talking about leveraging LLVM's parser, which is great, but I have to wonder if there isn't more commonality being left on the table. Just throwing

Re: [lldb-dev] RFC: Moving debug info parsing out of process

2019-02-26 Thread Frédéric Riss via lldb-dev
> On Feb 26, 2019, at 4:52 PM, Zachary Turner wrote: > > > > On Tue, Feb 26, 2019 at 4:49 PM Frédéric Riss > wrote: > >> On Feb 26, 2019, at 4:03 PM, Zachary Turner > > wrote: >> >> I would probably build the server by using mostly code

Re: [lldb-dev] RFC: Moving debug info parsing out of process

2019-02-26 Thread Zachary Turner via lldb-dev
On Tue, Feb 26, 2019 at 4:49 PM Frédéric Riss wrote: > > On Feb 26, 2019, at 4:03 PM, Zachary Turner wrote: > > I would probably build the server by using mostly code from LLVM. Since > it would contain all of the low level debug info parsing libraries, i would > expect that all knowledge of

Re: [lldb-dev] RFC: Moving debug info parsing out of process

2019-02-26 Thread Frédéric Riss via lldb-dev
> On Feb 26, 2019, at 4:03 PM, Zachary Turner wrote: > > I would probably build the server by using mostly code from LLVM. Since it > would contain all of the low level debug info parsing libraries, i would > expect that all knowledge of debug info (at least, in the form that compilers >

Re: [lldb-dev] RFC: Moving debug info parsing out of process

2019-02-26 Thread Zachary Turner via lldb-dev
I would probably build the server by using mostly code from LLVM. Since it would contain all of the low level debug info parsing libraries, i would expect that all knowledge of debug info (at least, in the form that compilers emit it in) could eventually be removed from LLDB entirely. So, for

Re: [lldb-dev] RFC: Moving debug info parsing out of process

2019-02-26 Thread Frédéric Riss via lldb-dev
> On Feb 25, 2019, at 10:21 AM, Zachary Turner via lldb-dev > wrote: > > Hi all, > > We've got some internal efforts in progress, and one of those would benefit > from debug info parsing being out of process (independently of whether or not > the rest of LLDB is out of process). > >

[lldb-dev] [lldb-mi] unable to debug GTK applications

2019-02-26 Thread Eran Ifrah via lldb-dev
Hi, I am not sure if this is the correct mailing list for this question, so excuse me if its not. I am trying a GTK application using lldb-mi, however, the application terminates immediately with the error message: @"15:47:16: Error: Unable to initialize GTK+, is DISPLAY set properly?\r\n"

Re: [lldb-dev] [RFC]The future of pexpect

2019-02-26 Thread Pavel Labath via lldb-dev
On 25/02/2019 22:15, Davide Italiano wrote: On Fri, Feb 22, 2019 at 6:32 AM Pavel Labath wrote: On 21/02/2019 19:48, Ted Woodward wrote: -Original Message- From: lldb-dev On Behalf Of Pavel Labath via lldb-dev Sent: Thursday, February 21, 2019 8:35 AM To: Davide Italiano Cc: