[M3devel] m3gdb broken

Mika Nystrom mika at async.caltech.edu
Sat Apr 2 04:42:33 CEST 2011

Jay K writes:
>But that "custom information" is largely just basic type information=2C tha=
>t any decent
>C compiler/debug-info/debugger can handle.
>Someone should investigate if we really pass stuff through that can't be we=
>ll represented
>in gcc's type information.
>For example: sub ranges? sets? enums? packed?

Subranges, sets, and enums certainly used to be shown in a "friendly" way
by m3gdb.


More information about the M3devel mailing list