Hi,

my system is running with powerpc and linux, i am facing some kernel crash problem.
can any body help me on this crash,i have pasted the trace and log

Program terminated with signal 11, Segmentation fault.
#0 memset (dstpp=0xd2, c=<value optimized out>, len=3374)
at ../../../src/Common/OS/linux/memset.c:20
20 ../../../src/Common/OS/linux/memset.c: No such file or directory.
in ../../../src/Common/OS/linux/memset.c

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
(1) Display the backtrace for the thread that crashed.

#0 memset (dstpp=0xd2, c=<value optimized out>, len=3374)
at ../../../src/Common/OS/linux/memset.c:20
#1 0x100e76c4 in LPREncode (pEnc=0x5b1debc8, pRTPPacket=0x5be69ee4)
at ../../../src/Common/comm/lpr/lpr.c:647
#2 0x100dde50 in RTPChanWork (pChan=<value optimized out>)
at ../../../src/Common/comm/rtpchan/rtpchan.c:2699
#3 0x100de5d8 in RTPTxTask (userDefined=<value optimized out>)
at ../../../src/Common/comm/rtpchan/rtpchan.c:2853
#4 0x1051d744 in pthread_entry (args=<value optimized out>)
at ../../../src/Common/OS/linux/psosapi/pthreadapi.c:222
#5 0x0ffaadec in start_thread (arg=<value optimized out>)
at pthread_create.c:298
#6 0x0f892530 in clone () from /lib/libc.so.6
Previous frame inner to this frame (corrupt stack?)

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
(2) Display argument parameters and local variables for the thread.

dstpp = (void *) 0xd2
c = <value optimized out>
len = 3374
xlen = <value optimized out>
cccc = <value optimized out>
dstp = 210


Rgds,
GoGear

You don't need us.
You have a segmentation fault. I didn't know PPC did segmentation errors, I thought it was an Intel thing, but it's a memory error, sufficiently glaring for the kernel to laugh at you.

You have debugging symbols, pointing to files and line numbers in your source. Have a look around. What matters in a crash is usually the very first error, which then spawns a dramatic series of other errors as the program goes down in a tailspin. It's the first error you need to fix.

I found this which seems to specifically identify your problem over at:

http://www.spinics.net/lists/newbies/msg42631.html

The error this guy had is identical to yours.

KaBar's Edge


On Wed, Feb 23, 2011 at 11:58 PM, Praveen kumar <chatpravi@xxxxxxxxx> wrote:
> Hi,
> I have an embedded system on which i get crash (Caused by memset ) at long
> run( Reproducible 2/10 times ),
> I wanted to know efficient ways (materials) to handle memset crashes .
>
> Program terminated with signal 11, Segmentation fault.
>
> #0 memset (dstpp=0xd2, c=<value optimized out>, len=3374)
> at ../../../src/Common/OS/linux/memset.c:20
> 20 ../../../src/Common/OS/linux/memset.c: No such file or directory.
> in ../../../src/Common/OS/linux/memset.c


The problem is probably that memset has been passed either a bad
pointer, or a bad size.

>From your backtrace, the dstpp of 0xd2 is almost certainly the
problem. The first 4K (and sometimes 64K) starting at location zero is
invalid. Passing a pointer in that range will cause an page fault (or
segmentation fault).

memset doesn't do any parameter checking, so if you want parameter
checking you'll need to do that yourself. You could add a function
like my_memest and use a macro to map memset to my_memset. Or you
could play with LD_PRELOAD (if your runtime library is in a shared
library) and intercept the calls that way.

http://stackoverflow.com/questions/6...inux-sys-calls
http://developers.sun.com/solaris/ar...sers_code.html
http://www.jayconrod.com/cgi/view_post.py?23

Yet another technique is to use the linker's wrap capability
http://stackoverflow.com/questions/9...-without-dlsym

Dave Hylands

Hi all,
Thanks for the response

as per the http://www.spinics.net/lists/newbies/msg42631.html response
we cont memset from location 0 to 64k, but as a Linux kernel i hope it wont allow user to give such a address which is protected.if at all it shows that dstpp=0xd2 in my log there is a change that this address may be virtual address(i may be wrong). please comment.