Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.

Notices

Welcome to LinuxQuestions.org, a friendly and active Linux Community.

You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!

Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.

If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.

Having a problem logging in? Please visit this page to clear all LQ-related cookies.

Introduction to Linux - A Hands on Guide

This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.

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.

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.

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.