Re: Gdb debugger issue on M1 Mac

[Marcus Wilson]

Good Day,

Because you are running this inside of the container  I would suspect it more likely docker restricting the process than the host. At least that's been my experience with macOS.

What flags are you passing to docker run?

Referencing the run documentation, specifically this section https://docs.docker.com/engine/reference/run/#runtime-privilege-and-linux-capabilities it looks like you could try adding the --privileged flag, or might try  --cap-add=SYS_PTRACE there are several cap-add options. 

I'd point out that this is the directory discussion list so probably not the best for this inquiry.

I hope this helps you out!

Marcus

On Tue, Mar 1, 2022, at 8:15 AM, Arun Thomas M wrote:

Joel

Thank you very much for your response. Greatly appreciate it.

Please allow me to ask yourself one thing. SIP is by default there to protect the folders required to safeguard critical system components. Disabling SIP is not recommended by Apple.

Having said that, do you suggest to try the same after disabling the SIP?

Looking forward to your response.

Arun

> On 01-Mar-2022, at 5:41 PM, Joël Krähemann <joel.kraehemann@gmail.com> wrote:

> 

> Hi,

> 

> I think it is about SIP (System Integrity Protection) but unsure.

> 

> regards,

> Joël

> 

> Am Di., 1. März 2022 um 05:58 Uhr schrieb Arun Thomas M

> <arun.thomas@ample.co.in>:

>> 

>> Dear Team,

>> 

>> I have downloaded and installed Docker for Apple Silicon on my

>> impressive M1 Mac. I could successfully install Ubuntu (linux/amd64).

>> Then I installed C and C++. Everything went well. Then I wrote a

>> simple C code ‘Hello World’. It generated the result. But when I tried

>> to run GNU’s gdb debugger, it showed errors that there were no

>> breakpoints. After running ‘gdb tst’, error generated was "Temporary

>> breakpoint 1 at 0x1149: file test.c, line 2. Starting program: /tst,

>> Warning: Could not trace the inferior process. Warning: trace:

>> Function not implemented. During startup program exited with code 127.

>> (gdb)

>> 

>> Your help would be much appreciated.

>> 

>> Thank you,

>> Arun