| Summary: | Capture valgrind initialization problems directly in eclipse | ||
|---|---|---|---|
| Product: | [Tools] Linux Tools | Reporter: | Jorge Costa <jmecosta> |
| Component: | Valgrind | Assignee: | Roland Grunberg <rgrunber> |
| Status: | RESOLVED DUPLICATE | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P3 | CC: | akurtakov, elaskavaia.cdt |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Whiteboard: | |||
|
Description
Jorge Costa
This can be fixed by checking the valgrind log files, if the a core file is in the folder than do not parse this file since it will cause exception
protected IValgrindMessage[] parseLogs(IPath outputPath) throws IOException, CoreException {
List<IValgrindMessage> messages = new ArrayList<IValgrindMessage>();
for (File log : outputPath.toFile().listFiles(LOG_FILTER)) {
if ( !log.toString().contains("core")) {
System.out.println("Launch Core Parser Create");
System.out.println(log.getName());
ValgrindCoreParser parser = new ValgrindCoreParser(log, launch);
System.out.println("Parser Launched");
System.out.println(parser.toString());
IValgrindMessage[] results = parser.getMessages();
messages.addAll(Arrays.asList(results));
createMarkers(results);
}
}
return messages.toArray(new IValgrindMessage[messages.size()]);
}
Roland, would you please take a look at this ? It sounds like a good thing to do. The core dump issue is fixed Bug 482906 Marking as duplicate. *** This bug has been marked as a duplicate of bug 482906 *** |