Re: [Crash-utility] [PATCH] Fixed the segment fault when ikconfig passed nonstandard values
> Some strange reasons may cause kcore to collect some strange
> entries of ikconfig, such as CONFIG_SECU+[some hex data] causes
Could you tell me the example of such CONFIG_SEC+[some hex data] that
causes the val to have NULL. I tried to reproduce but failed.
I guess you mean CONFIG_SECU+[some hex data] to be **strings that don't
contain the delimitor string '='** and then strtok_r() interprets
it as consisting of a single token, hence val resulting in having NULL.
If so, I think it's better to write so.
OTOH, due to the cause of this issue, is there also possibility
that the broken line contains two or more '=' and broken name
and values are appended in the ikconfig list? It has to be less
important than here because it doesn't result in segfault, but
it might be necessary to deal with it too depending on its actual impact.
Thanks.
HATAYAMA, Daisuke