[cfe-dev] Help needed finding out where sema diagnoses deprecated special functions

[Jonathan Coe via cfe-dev]

Thanks, the function name will let me put a break point in and start seeing
source.

I'm mystified as to why I don't get source info without any break points in
place. That issue does not see confined to clang's code.

Jon

On 24 February 2016 at 09:47, Nikola Smiljanic <popizdeh at gmail.com> wrote:

> I can't give you concrete answer but here's a hint or two that might help.
>
> When debugging, are you passing -cc1 to the process. If not you're
> invoking the driver and it never executes Sema code, it starts a new
> process to get actual compilation done.
> I guess you know about diagnostic text being inside .td files. Sometimes
> it's hard to find the identifier for a specific diagnostic because the text
> in .td file is not identical to diagnostic that's emitted. I put a
> breakpoint in DiagnosticBuilder::Emit whenever I have trouble finding the
> exact place where diagnostic is being emitted from.
> I'd be very surprised if the logic for detecting this issue is far from
> code that emits the diagnostic. Just follow the condition.
>
> On Wed, Feb 24, 2016 at 8:24 PM, Jonathan Coe via cfe-dev <
> cfe-dev at lists.llvm.org> wrote:
>
>> I'm trying to find out where clang finds deprecated compiler-generated
>> special member functions so I can update a clang tidy check I am working on
>> to apply the same logic.
>>
>> http://reviews.llvm.org/D16376
>>
>> I'm not sure where to start looking. I have some simple test code that
>> triggers the warning I want but asking LLDB to stop at program entry when
>> debugging clang won't print out source. I can explicitly print out source
>> lines but it won't show me which line I'm at. This renders exploration
>> impossiblel, I fear there's a trick I'm missing.
>>
>> I've tried searching code for diagnostic text but this seems to happen a
>> fair way away from diagnosing the issue.
>>
>> thanks for any help,
>>
>> Jon
>>
>> _______________________________________________
>> cfe-dev mailing list
>> cfe-dev at lists.llvm.org
>> http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-dev
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/cfe-dev/attachments/20160224/2cff6961/attachment.html>