Silvio Knizek

OK, was a problem on my side. My `$PATH` was not adjusted at the moment `ble-attach` run, so only the macOS inbuilt `awk` was available.

I can provide you the following data on a recent macOS 12.3.1 ```text $ /usr/bin/awk --version awk version 20200816 ``` ```text $ what /usr/bin/awk /usr/bin/awk PROGRAM:awk PROJECT:awk-32 PROGRAM:awk PROJECT:awk-32 ```...

I asked in the [Apple Developer Forums](https://developer.apple.com/forums/thread/705559).

Oh, and on macOS, the locale is called `en_US.UTF-8`, not `en_US.utf8`.

I understand that `cat -A` is only used for test. Is there some way to profile the called scripts to check why multiple cores get used 100% by `bash` processes?...

OK. Any way to profile/debug such loops?

Sorry for the delay. Here is some `pstree`. ```bash |-+- 28529 killermoehre -bash | \-+- 28530 killermoehre -bash | |--- 28531 killermoehre -bash | \-+- 28533 killermoehre -bash | \---...

> * **Q1**: In the `pstree` result that you have provided, there are two gawk instances. Which one is related to the Bash of 100% CPU usage? Or both gawks...

> * **Q8**: When it hangs, is the message `loading history...` always shown? No, only when I try to access the history by using `arrow_up` to get the last command....

Why not launching the process via `launchd`/`systemd` instead? For the username and password prompt both frameworks offer a solution.