ripgrep ignores /usr/bin/

[biburepo]

I am trying to unveil a few quirks in VirtualBox.
It seems that there might be something interesting in a file called "VBoxClient-all".
So I tried to find that file.

I am very happy that 'rg' can do this kind of search, so I don't have to remember the syntax and all the flags and options in 'locate'.

Let start at the end :)

This works :
# locate VBoxClient-all

/usr/bin/VBoxClient-all

This does not work :
# rg --no-messages --files / --iglob "VBoxClient-all"
[no output]

NOTE
This gives 8 hits :
# rg --no-messages --files / --iglob "VBoxClient" | wc -l
This gives 10 hits :
# locate -i VBoxClient | wc -l
The difference is 2 files in "/usr/bin/".

I tried, but nothing worked :
# rg --no-messages --files --unrestricted / --iglob "VBoxClient-all"

# rg --no-messages --files --u / --iglob "VBoxClient-all"

# rg --no-messages --files --no-ignore / --iglob "VBoxClient-all"

I must be missing something ?
There has to be a way to make 'rg' NOT ignore any directory ?

[BurntSushi]

Please provide an MRE. I cannot reproduce:

$ sudo touch /usr/bin/VBoxClient-all
$ rg --no-messages --files / --iglob VBoxClient-all
/usr/bin/VBoxClient-all

[biburepo]

Obviously it's not a matter of "/usr/bin".
Because this works :
# rg --no-messages --files / --iglob "xzless"

/usr/bin/xzless

However, what could be the problem with "VBoxClient-all" ?
root@vbf:# ls -laH /usr/bin/VBoxClient-all

-rwxr-xr-x 1 root root 1626 jul 9 2020 /usr/bin/VBoxClient-all

[BurntSushi]

Please provide an MRE.

Consider looking at the output of --debug.

[biburepo]

It's past midnight here (Netherlands).
I'll be back tomorrow, ehm, later today that is.

Might sound stupid but I don't know what "MRE" means :(

Another thing : can ik pipe the output of "--debug" to a file ?
Simpleminded '> debug-001.txt' doesn't work.

[BurntSushi]

https://en.wikipedia.org/wiki/Minimal_reproducible_example

> debug-001.txt doesn't work because logs are printed to stderr. Try 2> debug-001.txt to get just stderr or &> debug-001.txt to get both stdout and stderr.

Based on these questions, I think you might have better luck in a beginners forum. Or even better, if you know someone who can stand over your shoulder to help you troubleshoot, that would be the best.