https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217562
Bug ID: 217562
Summary: emulators/linux_base-c7: strange path truncating when
exec'ing in bash scripts
Product: Ports & Packages
Version: Latest
Hardware: Any
OS: Any
Status: New
Severity: Affects Only Me
Priority: ---
Component: Individual Port(s)
Assignee: [email protected]
Reporter: [email protected]
Assignee: [email protected]
Flags: maintainer-feedback?([email protected])
Hi,
I found a strange issue when running linux's bash scripts:
If you try to exec from a shell script (ran from /compat/linux/bin/bash) into
another, the exec'ed script path will be truncated by 8 bytes from the left
(and will obviously result in a failure).
Simple demonstrator, file 1 is "test_linux_exec_bash.sh":
#!/usr/bin/env bash
echo $0
exec ./test_linux_exec_bash_2.sh
file 2 is "test_linux_exec_bash_2.sh":
#!/usr/bin/env bash
echo $0
Then the result:
% /compat/linux/bin/bash ./test_linux_exec_bash.sh
./test_linux_exec_bash.sh
/compat/linux/usr/bin/env: zhe/tmp/test_linux_exec_bash_2.sh: No such file or
directory
This will not happen if the 1st script try to exec into a binary
(/compat/linux/usr/bin/env issue??)
I've ran the demo through ktrace, but it revealed nothing really interesting:
at some point after execing into env, the path is corrupted... valgrind can't
be run on linux binaries, so I did not found anything on that front...
At that point, I'm failing to see what is going wrong here.
Any ideas? Thanks
--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
[email protected] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-emulation
To unsubscribe, send any mail to "[email protected]"
