[Buildroot] [Bug 12866] should we be disabling bash executable path caching?

bugzilla at busybox.net bugzilla at busybox.net
Mon May 11 12:06:35 UTC 2020


--- Comment #2 from Matt Weber <matthew.weber at rockwellcollins.com> ---
Thinking about it a little more, the actual shell script would need to set 'set
+h' but my understanding is the executable hash table (for quick lookup after a
commend is executed the first time) is just local to the current script's
context.  So to cause an issue, you would have to call the same command twice
in the same script and move the location of the executable without updating the
PATH.  That doesn't sound normal.  I'll close this bug :-)

You are receiving this mail because:
You are on the CC list for the bug.

More information about the buildroot mailing list