[cdt-dev] Debugging a content assist bug involving libhover

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]

[cdt-dev] Debugging a content assist bug involving libhover

From: Nathan Ridge <zeratul976@xxxxxxxxxxx>
Date: Wed, 11 Jan 2017 21:38:50 +0000
Accept-language: en-CA, en-US
Delivered-to: cdt-dev@xxxxxxxxxxx
List-archive: <https://dev.eclipse.org/mailman/private/cdt-dev>
List-help: <mailto:cdt-dev-request@eclipse.org?subject=help>
List-subscribe: <https://dev.eclipse.org/mailman/listinfo/cdt-dev>, <mailto:cdt-dev-request@eclipse.org?subject=subscribe>
List-unsubscribe: <https://dev.eclipse.org/mailman/options/cdt-dev>, <mailto:cdt-dev-request@eclipse.org?subject=unsubscribe>
Thread-index: AQHSbFJ0RTTSdZDT8E6TkXkMbnnrZA==
Thread-topic: Debugging a content assist bug involving libhover

I'm looking into a content assist bug (bug 391439) which requires libhover to be present to reproduce.

Libhover comes from another project/repository (org.eclipse.linuxtools), so in my usual development environment (where I check out and build org.eclipse.cdt) I cannot reproduce the issue.

What is the usual workflow for debugging an issue like this that requires components from two different projects? How would one write a test for a bug like this?

Thanks,
Nate

Follow-Ups:
- Re: [cdt-dev] Debugging a content assist bug involving libhover
  - From: Nathan Ridge

Prev by Date: Re: [cdt-dev] Grouping error reports by original exception
Next by Date: Re: [cdt-dev] Debugging a content assist bug involving libhover
Previous by thread: [cdt-dev] Grouping error reports by original exception
Next by thread: Re: [cdt-dev] Debugging a content assist bug involving libhover
Index(es):
- Date
- Thread

Breadcrumbs