Bug 418440 - Executable files with dots in their names aren't detected as such
Summary: Executable files with dots in their names aren't detected as such
Status: NEW
Alias: None
Product: CDT
Classification: Tools
Component: cdt-debug (show other bugs)
Version: 8.2.1   Edit
Hardware: PC Linux
: P3 minor (vote)
Target Milestone: ---   Edit
Assignee: cdt-debug-inbox@eclipse.org CLA
QA Contact: Jonah Graham CLA
URL:
Whiteboard:
Keywords: consistency
Depends on:
Blocks:
 
Reported: 2013-10-01 13:10 EDT by Samuel Oggier CLA
Modified: 2020-09-04 15:20 EDT (History)
4 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Samuel Oggier CLA 2013-10-01 13:10:03 EDT
*Issue:*
The executable scan (binary parser / ELF parser) does not seem to pick up executables (ELF32 in this case) with dots in their names,
e.g. maven style names like "com.domain-artefact-0.0.1-SNAPSHOT-test_runner".
Dots at the end don't cause problems, dots at the beginning cause the file to be hidden anyway (at least on linux).

*How to reproduce:*
1. Add a dot in the middle of an executables filename => the file is now displayed as an unknown/text file type
2. Try to auto-detect that binary with 'Run' -> 'Run As' -> 'Local C/C++ Application' => Error: "Launch failed. Binary not found".

*Suggestion:*
The first guess is, that aforementioned files get discarded by an extension based filter.
File extensions might be checked for performance reasons,
so a possible solution could be to exclude files with known
or perhaps some form of reasonable extensions (e.g. 1-4 letters or digits).

-- Configuration Details --
Product: Eclipse 2.0.1.20130919-0803 (org.eclipse.epp.package.cpp.product)
Installed Features:
 org.eclipse.platform 4.3.1.v20130911-1000
Comment 1 Samuel Oggier CLA 2013-10-01 13:24:43 EDT
Possibly related to: https://bugs.eclipse.org/bugs/show_bug.cgi?id=364027
Comment 2 Jonah Graham CLA 2019-12-30 18:55:17 EST
This bug was assigned and targeted at a now released milestone (or Future or Next that isn't being used by CDT). As that milestone has now passed, the milestone field has been cleared. If this bug has been fixed, please set the milestone to the version it was fixed in and mark the bug as resolved.