Re: [MiNT] XaAES crash errors

[Paul Wratt <paul.wratt@gmail.com>]

On Fri, Dec 4, 2009 at 1:03 PM, Paul Wratt <paul.wratt@gmail.com> wrote:
> Can anyone tell me what this means:
> pid  57 (xaaes): run_km(\c\MINT\1-16-cur\XAAES\xaaes.km) ok (bp 0x4A7E000)!
> pid 58 (AESSYS): KM_TRACE: unregister failed?!
> pid 58 (AESSYS): XaAES:../k_init.c,220: kfree on 0x4AEBE44, invalid
> STAT_MAGIC! FATAL ERROR. You must reboot the system.
>
> k_init.c,220 is not something I have changed (presuming its a line
> number), but I realise what kfree is. What I dont currently understand
> is "unregister" and STAT_MAGIC.
>
> Cheers
>
> Paul
>

Also, can anyone tell me how to initialize a CHAR var when you dont
know what the max length will. I have had no success in either a net
search, or looking through the code (for other uses of it)

Also some ideas as to how to create "standard" structs at compile time:
struct xa_gradient
{
	struct xa_data_hdr *allocs;
	short wmask, hmask;
	short w, h;
	short method;
	short n_steps;
	short steps[8];
	struct rgb_1000 c[16];
};

 that can support dynamic (runtime) changes to the following formats:
struct xa_gradient otop_vslide_gradient =
{
	NULL,
	-1, 0,
	 0, 16,

	1, 0, {0},
	{{400,400,500},{600,600,700}},
};

static struct xa_gradient slist_otop_info_gradient =
{
	NULL,
	0, -1,
	16, 0,

	3, 1, {3, 0},
	{{200,200,200},{600,600,600},{900,900,900}},
};

Or am I mis-reading how C stores the final structs in the binary
(which is actually as "xa_gradient" is defined)


Any idea or comments are welcome, otherwise "no early christmas presents"..

Paul