> > +
> > +void bgenv_map_uservar(uint8_t *udata, char **key, char **type, uint8_t
> > **val,
> > + size_t *record_size, size_t *data_size)
> > +{
> > + /* Each user variable is encoded as follows:
> > + * |------------|------------|-------------|----------------|
> > + * | char KEY[] | size_t len | char type[] | uint8_t data[] |
>
> Is this the storage format? In that case, it leaves some open questions
> regarding the widths of the type:
>
> - size_t depends on the platform. Better use some uintX_t.
Uff, that would indeed cause trouble if cross-compiling and pre-filling
a target's environment with a different, natively built tool and later
reading it with the cross-compiled tool with both tools having
a different size_t size. Big thanks for seeing this!
--
Andreas Reichel
Dipl.-Phys. (Univ.)
Software Consultant
[email protected], +49-174-3180074
TNG Technology Consulting GmbH, Betastr. 13a, 85774 Unterfoehring
Geschaeftsfuehrer: Henrik Klagges, Dr. Robert Dahlke, Gerhard Mueller
Sitz: Unterfoehring * Amtsgericht Muenchen * HRB 135082
--
You received this message because you are subscribed to the Google Groups "EFI
Boot Guard" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/efibootguard-dev/20170912102608.GC27820%40iiotirae.
For more options, visit https://groups.google.com/d/optout.
