topic Re: memory corruption imx28 in i.MX Processors

memory corruption imx28

shashikanthirem — Fri, 18 Sep 2020 22:36:17 GMT

i have built LTIB imx28 based application, multiprocessor and multithreading environment, by some activating event

Ltib kernel version is 2.6.35.10,

Now I cannot migrate to any other version apart fixing bug in our program

i am getting memory corrupt issue ran on gdb

[New Thread 1133208688 (LWP 296)]
** glibc detected ** /PROGRAM: malloc(): memory corruption: 0x05b4cef8 ***

Program received signal SIGABRT, Aborted.

i tried valgrind but its showing illeagal instruction

ANY IDEA SUGGESTION HOW TO SOLVE

Re: memory corruption imx28

Bio_TICFSL — Mon, 21 Sep 2020 13:21:20 GMT

Hello shashikanthirem,

You've probably trashed the stack or heap. The error would suggest it's more likely to be the heap, but there's no guarantee stack corruption isn't the cause. The corruption is occurring prior to this function being called.

The SIGABRT signal can be caught, but it cannot be blocked; if the signal handler returns then all open streams are closed and flushed and the program terminates (dumping core if appropriate). This means that the abort call never returns. Because of this characteristic, it is often used to signal fatal conditions in support libraries, situations where the current operation cannot be completed but the main program can perform cleanup before exiting. It is used when an assertion fails.

Regards

Re: memory corruption imx28

shashikanthirem — Tue, 22 Sep 2020 04:05:11 GMT

if I run export MALLOC_CHECK_=1, run exe, the issue is not reproducing

but if power off unit and just run exe, issue comes immediately,

don't know debug further

@Bio_TICFSL : thanks i will check on this further.

Re: memory corruption imx28

shashikanthirem — Tue, 22 Sep 2020 08:16:42 GMT

can you give input on multi thread environment, how to narrow down issue causing that will be helpfull