We've thrown ECTF_DESCENDING for some time if this wasn't true. (In
theory this restriction could be lifted later on if necessary, but in
practice since this means adding the members in a different order from
their C declaration, this seems unlikely ever to be something anyone
would want to do.)
include/
* ctf-api.h (ctf_add_member): You cannot add struct members
backwards any more.
/* Add a member to a struct or union, either at the next available offset (with
suitable padding for the alignment) or at a specific offset, and possibly
with a specific encoding (creating a slice for you). Offsets need not be
- unique, and need not be added in ascending order. ctf_add_member_bitfield
+ unique, but must be added in ascending order. ctf_add_member_bitfield
with a nonzero bit_width will fail unless the struct was created with
CTF_ADD_STRUCT_BITFIELDS. */