arm-none-eabi-gdb missed in ubuntu 18.04

Status changed to 'Confirmed' because the bug affects multiple users.

The package name is (was) actually gdb-arm-none-eabi.

What happened here? Was ARM GDB intentionally left out of 18.04? This is a pretty important tool for anyone doing ARM development.

We can still install the 16.04 version (plus libreadline6 dependency) and it works okay in 18.04.

https://packages.ubuntu.com/xenial/gdb-arm-none-eabi
https://packages.ubuntu.com/xenial/libreadline6

Using gdb-multiarch seems to be an alternative.

I tried the gdb-multiarch and it gives me

"
warning: while parsing target description (at line 1): Target description specified unknown architecture "arm"
"

When trying to connect to STM32F427 (via st-link).

gdb-multiarch seemed like it should work.
I use openocd 0.10.0 but when I attempt a connection to it reports of my SAMD09D14A (on an Adafruit Seesaw)
"warning: Architecture rejected target-supplied description
...
Truncated register 16 in remote 'g' packetInfo : dropped 'gdb' connection"

This very helpful post provided the solution and got me here to see what was up:
https://acassis.wordpress.com/2018/12/27/adding-arm-none-eabi-gdb-to-ubuntu-18-04/

gdb-arm-none-eabi works perfectly!

I came across this while following the Apache mynewt blinky tutorial, with a nRF development board https://mynewt.apache.org/latest/tutorials/blinky/nRF52.html
The mynewt load target script has hard-coded the arm-none-eabi-gdb command -> not found error.

I managed to make it run by installing gdb-multiarch and adding a symlink:
apt install gdb-multiarch
ln -s /usr/bin/gdb-multiarch /usr/bin/arm-none-eabi-gdb

I just tried installing gdb-multiarch as a replacement for gdb-arm-none-eabi for an Atmel SAMD target and an STM32 target, and that worked out of the box. Maybe this issue can be closed?

A transitional package depending on gdb-multiarch might have been useful, but since this package has been gone for quite some while (also from Debian), I guess that's no longer so relevant.