| Summary: | Missing quoting around the path to basename in call stack display | ||
|---|---|---|---|
| Product: | Portage Development | Reporter: | Michał Górny <mgorny> |
| Component: | Core | Assignee: | Portage team <dev-portage> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | trivial | ||
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: | Patch adding missing quoting | ||
Created attachment 228983 [details, diff]
Patch adding missing quoting
*** This bug has been marked as a duplicate of bug 315727 *** |
Another simple issue, the dump_trace() function lacks quoting around the ${BASH_SOURCE} passed to basename. Due to that, whenever the ebuild/script path contains special characters, portage reports null source path and a basename call syntax error.