On Mon, Nov 24, 2014 at 4:26 PM, Eric Christopher
wrote:
>
>
> On Mon Nov 24 2014 at 11:20:11 AM Adrian Prantl wrote:
>
>>
>> > On Nov 24, 2014, at 9:22 AM, David Blaikie wrote:
>> >>
>> >> The debug info in foo.o will look like this::
>> >>
>> >> .debug_info.dwo
>> >
>> > (so if this goes in
On Mon Nov 24 2014 at 11:20:11 AM Adrian Prantl wrote:
>
> > On Nov 24, 2014, at 9:22 AM, David Blaikie wrote:
> >>
> >> The debug info in foo.o will look like this::
> >>
> >> .debug_info.dwo
> >
> > (so if this goes in debug_info.dwo then it would be in foo.dwo, not
> foo.o... but I had some
On Mon, Nov 24, 2014 at 11:20 AM, Adrian Prantl wrote:
>
> > On Nov 24, 2014, at 9:22 AM, David Blaikie wrote:
> >>
> >> The debug info in foo.o will look like this::
> >>
> >> .debug_info.dwo
> >
> > (so if this goes in debug_info.dwo then it would be in foo.dwo, not
> foo.o... but I had some
> On Nov 24, 2014, at 9:22 AM, David Blaikie wrote:
>>
>> The debug info in foo.o will look like this::
>>
>> .debug_info.dwo
>
> (so if this goes in debug_info.dwo then it would be in foo.dwo, not foo.o...
> but I had some further thoughts about this... )
>
> So - imagining a future in whi
On Fri, Nov 21, 2014 at 5:52 PM, Adrian Prantl wrote:
> Plans for module debugging
> ==
>
> I recently had a chat with Eric Christopher and David Blaikie to discuss
> ideas for debug info for Clang modules and this is what we came up with.
>
> Goals
> -
>
> Clang modul
