I tried bulding gdb 12.1 on macOS 12.4 with an Apple M1 chip, but it öooks like that target is not supported. Can I ask if there are plans to support that platform, or even work in progress that I could try out? (I'd use it for debugging Emacs on macOS.) TIA
Hi,
On 6/22/22 07:52, Gerd Möllmann via Gdb wrote:
> I tried bulding gdb 12.1 on macOS 12.4 with an Apple M1 chip, but it öooks like that target is not supported.
>
> Can I ask if there are plans to support that platform, or even work in progress that I could try out? (I'd use it for debugging Emacs on macOS.)
>
> TIA
Arm has macOS-hosted arm-none-eabi tools, but I don't think native aarch64 debugging on macOS is supported, as you said.
I can't speak for other contributors, but I don't know of any plan to support that OS/arch combination for GDB. We're open to
accepting patches though.
I think LLDB is the way to go on macOS.
> On Jun 22, 2022, at 4:57 AM, Luis Machado via Gdb <gdb@sourceware.org> wrote:
>
> Hi,
>
> On 6/22/22 07:52, Gerd Möllmann via Gdb wrote:
>> I tried bulding gdb 12.1 on macOS 12.4 with an Apple M1 chip, but it öooks like that target is not supported.
>> Can I ask if there are plans to support that platform, or even work in progress that I could try out? (I'd use it for debugging Emacs on macOS.)
>> TIA
>
> Arm has macOS-hosted arm-none-eabi tools, but I don't think native aarch64 debugging on macOS is supported, as you said.
>
> I can't speak for other contributors, but I don't know of any plan to support that OS/arch combination for GDB. We're open to
> accepting patches though.
>
> I think LLDB is the way to go on macOS.
Unfortunately that seems to be the only option right now, but it's a nasty one. The UI is obnoxious, and it can't debug GCC output at all unless it was compiled with -O0.
paul
On 6/22/22 14:01, Paul Koning wrote:
>
>
>> On Jun 22, 2022, at 4:57 AM, Luis Machado via Gdb <gdb@sourceware.org> wrote:
>>
>> Hi,
>>
>> On 6/22/22 07:52, Gerd Möllmann via Gdb wrote:
>>> I tried bulding gdb 12.1 on macOS 12.4 with an Apple M1 chip, but it öooks like that target is not supported.
>>> Can I ask if there are plans to support that platform, or even work in progress that I could try out? (I'd use it for debugging Emacs on macOS.)
>>> TIA
>>
>> Arm has macOS-hosted arm-none-eabi tools, but I don't think native aarch64 debugging on macOS is supported, as you said.
>>
>> I can't speak for other contributors, but I don't know of any plan to support that OS/arch combination for GDB. We're open to
>> accepting patches though.
>>
>> I think LLDB is the way to go on macOS.
>
> Unfortunately that seems to be the only option right now, but it's a nasty one. The UI is obnoxious, and it can't debug GCC output at all unless it was compiled with -O0.
Technically we have darwin native support for x86-64 (don't know how well it works). If that works well, It might be a matter of implementing the native parts for aarch64.
> On Jun 22, 2022, at 9:06 AM, Luis Machado <luis.machado@arm.com> wrote:
>
> On 6/22/22 14:01, Paul Koning wrote:
>>> On Jun 22, 2022, at 4:57 AM, Luis Machado via Gdb <gdb@sourceware.org> wrote:
>>>
>>> Hi,
>>>
>>> On 6/22/22 07:52, Gerd Möllmann via Gdb wrote:
>>>> I tried bulding gdb 12.1 on macOS 12.4 with an Apple M1 chip, but it öooks like that target is not supported.
>>>> Can I ask if there are plans to support that platform, or even work in progress that I could try out? (I'd use it for debugging Emacs on macOS.)
>>>> TIA
>>>
>>> Arm has macOS-hosted arm-none-eabi tools, but I don't think native aarch64 debugging on macOS is supported, as you said.
>>>
>>> I can't speak for other contributors, but I don't know of any plan to support that OS/arch combination for GDB. We're open to
>>> accepting patches though.
>>>
>>> I think LLDB is the way to go on macOS.
>> Unfortunately that seems to be the only option right now, but it's a nasty one. The UI is obnoxious, and it can't debug GCC output at all unless it was compiled with -O0.
>
> Technically we have darwin native support for x86-64 (don't know how well it works). If that works well, It might be a matter of implementing the native parts for aarch64.
The x86-64 Darwin GDB has been useable for me in the past, so yes, an aarch64 port of that would be a promising notion and should do a much better job debugging optimized code.
paul