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

2019-03-06 Thread Adrian Prantl via lldb-dev
> On Mar 6, 2019, at 9:43 AM, Zachary Turner wrote: > > > On Mon, Mar 4, 2019 at 10:32 AM Zachary Turner > wrote: > On Sat, Mar 2, 2019 at 2:56 PM Adrian Prantl > wrote: >> It becomes testable as an independent component, because you can

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

2019-03-06 Thread Zachary Turner via lldb-dev
On Mon, Mar 4, 2019 at 10:32 AM Zachary Turner wrote: > On Sat, Mar 2, 2019 at 2:56 PM Adrian Prantl wrote: > >> >>- It becomes testable as an independent component, because you can >>just send requests to it and dump the results and see if they make sense. >>Currently there is

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

2019-03-04 Thread Zachary Turner via lldb-dev
On Sat, Mar 2, 2019 at 2:56 PM Adrian Prantl wrote: > > On Feb 25, 2019, at 10:21 AM, Zachary Turner via lldb-dev < > lldb-dev@lists.llvm.org> 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

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

2019-03-02 Thread Davide Italiano via lldb-dev
On Sat, Mar 2, 2019 at 2:56 PM Adrian Prantl via lldb-dev wrote: > > > > 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

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

2019-03-02 Thread Adrian Prantl 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). > >

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

2019-03-01 Thread J.R. Heisey via lldb-dev
Hi Guys, https://wiki.eclipse.org/TCF#Where_can_I_Read_Documentation.3F I hope you don't mind me chiming in I've been following this thread. I am a little familiar with the Eclipse Target Communications Framework (TCF).

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

2019-03-01 Thread Zachary Turner via lldb-dev
On Wed, Feb 27, 2019 at 4:35 PM Frédéric Riss wrote: > > On Feb 27, 2019, at 3:14 PM, Zachary Turner wrote: > > > > On Wed, Feb 27, 2019 at 2:52 PM Frédéric Riss wrote: > >> On Feb 27, 2019, at 10:12 AM, Zachary Turner wrote: >> >> >> >> For what it's worth, in an earlier message I mentioned

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

2019-02-27 Thread Frédéric Riss via lldb-dev
> On Feb 27, 2019, at 3:14 PM, Zachary Turner wrote: > > > > On Wed, Feb 27, 2019 at 2:52 PM Frédéric Riss > wrote: >> On Feb 27, 2019, at 10:12 AM, Zachary Turner > > wrote: > > >> For what it's worth, in an earlier message I mentioned

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

2019-02-27 Thread via lldb-dev
for it. --paulr From: Zachary Turner [mailto:ztur...@google.com] Sent: Wednesday, February 27, 2019 10:13 AM To: Robinson, Paul Cc: fr...@apple.com; lldb-dev@lists.llvm.org Subject: Re: [lldb-dev] RFC: Moving debug info parsing out of process GSYM, as I understand it, is basically just an evolution

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

2019-02-27 Thread Zachary Turner via lldb-dev
On Wed, Feb 27, 2019 at 2:52 PM Frédéric Riss wrote: > On Feb 27, 2019, at 10:12 AM, Zachary Turner wrote: > > > > For what it's worth, in an earlier message I mentioned that I would > probably build the server by using mostly code from LLVM, and making sure > that it supported the union of

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

2019-02-27 Thread Frédéric Riss via lldb-dev
> On Feb 27, 2019, at 10:12 AM, Zachary Turner wrote: > > > > On Tue, Feb 26, 2019 at 5:39 PM Frédéric Riss > wrote: > >> On Feb 26, 2019, at 4:52 PM, Zachary Turner > > wrote: >> >> >> >> On Tue, Feb 26, 2019 at 4:49 PM Frédéric Riss >

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

2019-02-27 Thread Sanimir Agovic via lldb-dev
Hi Zachary, On Mon, Feb 25, 2019 at 7:23 PM Zachary Turner via lldb-dev < lldb-dev@lists.llvm.org> wrote: > [...] > Thoughts? Having a standalone symbols interface would open many tooling possibilities, the available interfaces are too dwarfish and too primitive. This necessarily does not require

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

2019-02-27 Thread Zachary Turner via lldb-dev
thing specific to suggest. > > --paulr > > > > *From:* lldb-dev [mailto:lldb-dev-boun...@lists.llvm.org] *On Behalf Of > *Frédéric > Riss via lldb-dev > *Sent:* Tuesday, February 26, 2019 5:40 PM > *To:* Zachary Turner > *Cc:* LLDB > *Subject:* Re: [lldb-dev] RFC: Movin

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

2019-02-27 Thread Zachary Turner via lldb-dev
On Tue, Feb 26, 2019 at 5:39 PM Frédéric Riss wrote: > > 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 from

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

2019-02-26 Thread via lldb-dev
t throwing that thought out there; I don't have anything specific to suggest. --paulr From: lldb-dev [mailto:lldb-dev-boun...@lists.llvm.org] On Behalf Of Frédéric Riss via lldb-dev Sent: Tuesday, February 26, 2019 5:40 PM To: Zachary Turner Cc: LLDB Subject: Re: [lldb-dev] RFC: Moving debug in

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] RFC: Moving debug info parsing out of process

2019-02-25 Thread Zachary Turner via lldb-dev
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). There's a couple of advantages to this, which I'll enumerate here: - It improves one source