The list of micro controllers with the debugWIRE interface is very finite and does not evolve, because for more recent AVRs UPDI is the debugging interface of choice.
All the classic ATtiny chips that have a debugging interface can be debugged using debugWIRE. Further all ATmegaX8 (X=4,8,16,32) have a debugWIRE interface, but not the ATmega8 chip. And then there are a few ATmega MCUs that are not so well-known in maker cycles and not covered by well-maintained Arduino cores.
ATtiny (covered by MicroCore):
- ATtiny13
ATtinys (covered by the ATTinyCore):
- ATtiny43U
- ATtiny2313(A), ATtiny4313
- ATtiny24(A), ATtiny44(A), ATtiny84(A)
- ATtiny441, ATtiny841
- ATtiny25, ATtiny45, ATtiny85
- ATtiny261(A), ATtiny461(A), ATtiny861(A)
- ATtiny87, ATtiny167
- ATtiny828
- ATtiny48, ATtiny88
- ATtiny1634
ATmegas (covered by MiniCore):
ATmega48, ATmega48A, ATmega48PA, ATmega48PB,ATmega88, ATmega88A, ATmega88PA, Atmega88PB,- ATmega168, ATmega168A, ATmega168PA, ATmega168PB,
- ATmega328, ATmega328P, ATmega328PB
The ATmega48 and ATmega88 (without the A-suffix) that I have sitting on my desktop suffer from stuck-at-one bits in the program counter and are therefore not debuggable by GDB.
Other ATmegas:
- ATmega8U2, ATmega16U2, ATmega32U2
- ATmega32C1, ATmega64C1, ATmega16M1, ATmega32M1, ATmega64M1
- AT90USB82, AT90USB162
- AT90PWM1, AT90PWM2B, AT90PWM3B
- AT90PWM81, AT90PWM161
- AT90PWM216, AT90PWM316
- ATmega8HVA, ATmega16HVA, ATmega16HVB, ATmega32HVA, ATmega32HVB, ATmega64HVE2