Re: Segmentation fault while running some applications!

Thanks Steve,

Point no. 1 and 4 dont apply in my case because i have compiled
iptables along with the file system applications. I will check rest of
the two options and let u know.

And the answer for your question for my other programs is that some
other applications e.g. df is also causing same issue. While rest of
the applications are working properly. I downloaded a pre-build image
of file-system that contained 'df' utility, in that case df was
working perfect.


On Tue, Dec 18, 2012 at 8:27 PM, Steve deRosier <[email protected]> wrote:
> On Tue, Dec 18, 2012 at 4:58 AM, Arshan Awais <[email protected]> wrote:
>> Hi Greg,
>>
>> I recompiled my kernel and used "None" option instead of uClibc,
>> uC-libc or glibc in menuconfig. (because i am also having issues in
>> compilation when i select options other than 'None' while library
>> selection)
>> This time when i ran iptables -v, i got the following dump:
>>
>> iptables[377] killed because of sig - 11
>>
>
> You sort of need a C library for any C code you're working with. I
> suppose if you're hand-writing assembly code, you wouldn't need it,
> but, last I looked iptables is C code and should require to link
> against a C library of some sort. If you're getting successful
> compilation and link and not building any of the three supported C
> libraries, then you've got pretty big problems. Depending on your
> environment, I see one of the following possibilities:
>
> 1. You're actually not building a cross-compiled image for your
> target. In other words: you're building using your host's compilers
> targeting your host computer. Then you're moving the exe to a
> different target processor and boom!
> 2. Your x-compiler is linking against some of it's preconfigured C
> libraries, if static, that's probably OK, but if it's a shared link,
> you'll need to push those into your filesystem image.
> 3. Your compiler is linking against some left-over objects, but those
> aren't getting inserted into your image because you've turned off the
> C libs.
> 4. All is well with your environment, and you've edited some code and
> inserted a read/write to an invalid address (most likely null) and you
> need to debug that.
>
> I'm sure there's more possibilities, but 4 seems like enough for now.
>
> If you're using a stock uClinux, and a stock target board, and a
> proper environment, most things should pretty well work out of the
> box. Do other programs function properly and iptables is the only
> thing that's failing? If that's the case, it's possible there's a bug
> in whatever version of iptables that you're working with. Or, you need
> to enable some feature it depends on that's not turned on by default.
>
> Just a few ideas, hope it helps.
>
> - Steve
> _______________________________________________
> uClinux-dev mailing list
> [email protected]
> http://mailman.uclinux.org/mailman/listinfo/uclinux-dev
> This message was resent by [email protected]
> To unsubscribe see:
> http://mailman.uclinux.org/mailman/options/uclinux-dev
_______________________________________________
uClinux-dev mailing list
[email protected]
http://mailman.uclinux.org/mailman/listinfo/uclinux-dev
This message was resent by [email protected]
To unsubscribe see:
http://mailman.uclinux.org/mailman/options/uclinux-dev