https://sourceware.org/bugzilla/show_bug.cgi?id=32207
Bug ID: 32207
Summary: [collect app] Error in parsing the -O option
Product: binutils
Version: 2.43.1
Status: NEW
Severity: normal
Priority: P2
Component: gprofng
Assignee: vladimir.mezentsev at oracle dot com
Reporter: ruud.vanderpas at oracle dot com
Target Milestone: ---
If I use a pathname, absolute or relative, with the -O option, the name seems
to be truncated and as a result, the directory cannot be found.
These experiments demonstrate the behaviour.
No problem in the local directory:
$ gprofng collect app -O test.er ../bindir/mxv-pthreads
Creating experiment directory test.er (Process ID: 1205025) ...
mxv: error check passed - rows = 2000 columns = 3000 threads = 1
But this fails:
$ gprofng collect app -O ../experiments/test.er ../bindir/mxv-pthreads
Store directory ../experiment is not accessible: No such file or directory
Using the absolute pathname does not help either:
$ gprofng collect app -O /home/ruud/02.demos/run-demodir/experiments/test.er
../bindir/mxv-pthreads
Store directory /home/ruud/02.demos/run-demodir/experiment is not accessible:
No such file or directory
$ ls -l ../experiments/
total 0
$
It looks like the last character in the pathname is chopped off. To test this,
I tried the name "experiment", not "experiments", and now there is a message
that "experimen" can not be found:
$ gprofng collect app -O ../experiment/test.er ../bindir/mxv-pthreads
Store directory ../experimen is not accessible: No such file or directory
$
--
You are receiving this mail because:
You are on the CC list for the bug.
