I have a question
i had a problem as soon as i installed my Debian lenny but its expanding

When i try to open epiphany or iceweasel i get this kind of error
and they never open.

This only happend with this two programs but now , i also have it on programs that used to work like Tilda

I have a guess that its a hard disk error but i am not shure if anyone knows please enlighten me.

Seg faults or segmentation faults are RAM memory errors.

http://web.mit.edu/10.001/Web/Tips/t...mentation.html

http://en.wikipedia.org/wiki/Segmentation_fault

So according to the links , there is an inside problem on the C++ code of he software i listed.
Isn it weird that one of them used to work but now it doesnt?? And i certainly didnt messed up with their core files.

And what about solutions anything suggested??

Segmentation faults can be caused by faulty ram, however that's not the only possible cause.

Technically, a segfault happens when a program tries to use ram which is out if his scope, or when it tries to use it in a way that's not supposed to. For example: trying to write on a read-only segment or something like that. So, any program that can do a buffer overflow is capable of segfaulting as well. Modern compiler, however, limit the amount of possible causes, because with each version they become better at predicting run-time errors (there are some cases where it's impossible to make a prediction, though).

working with pointers it's easy to create faulty code: referencing null or uninitialized pointers are possible causes, that includes lots of variants, like trying to operate on a file pointer without cheking if it's been successfully open or if it's value is correct and not garbage pointing elsewhere. But I am sure you don't really care about this.

Faulty ram can cause this because contents stored on (or retrieved from) a faulty memory cell can't be guaranteed to be trustable. If that cell held a pointer containing the offset for another variable, and it's a faulty cell, when you read it then odd things can happen, and the read value can point elsewhere, probably into an illegal region. That, of course, causes a segfault.

A borked compiled or toolchain can also produce that, as can crazy cflags and experimental packages. But if you don't compile your own binaries, then I suppose that's not your problem.

So, where to start? Pick a livecd that has memtest86+ as on its boot menu, and use it.

Thanks for the reply!

i have downloaded memtest86 but how do i tell it to start on boot-up so i can see if there are any errors??


Also i get this erors while booting and i want to know if they are connected to the RAM problem


Sep 20 01:35:05 noname kernel: [ 0.292307] system 00:01: ioport range 0x4d0-0x4d1 has been reserved
Sep 20 01:35:05 noname kernel: [ 0.292312] system 00:01: ioport range 0x290-0x29f has been reserved
Sep 20 01:35:05 noname kernel: [ 0.292316] system 00:01: ioport range 0x800-0x87f has been reserved
Sep 20 01:35:05 noname kernel: [ 0.292320] system 00:01: ioport range 0x290-0x294 has been reserved
Sep 20 01:35:05 noname kernel: [ 0.292324] system 00:01: ioport range 0x880-0x88f has been reserved
Sep 20 01:35:05 noname kernel: [ 0.292341] system 00:0a: ioport range 0x400-0x4bf could not be reserved
Sep 20 01:35:05 noname kernel: [ 0.292351] system 00:0b: iomem range 0xf0000000-0xf3ffffff could not be reserved
Sep 20 01:35:05 noname kernel: [ 0.292361] system 00:0c: iomem range 0xf0000-0xf3fff could not be reserved
Sep 20 01:35:05 noname kernel: [ 0.292365] system 00:0c: iomem range 0xf4000-0xf7fff could not be reserved
Sep 20 01:35:05 noname kernel: [ 0.292370] system 00:0c: iomem range 0xf8000-0xfbfff could not be reserved
Sep 20 01:35:05 noname kernel: [ 0.292374] system 00:0c: iomem range 0xfc000-0xfffff could not be reserved
.......
......and so on

memtest86 and memtest86+ are different programs. memtest86+ comes as an option in the boot menu of many livecds (and install cds as well), that's what I advice you to use, because it works outside the OS.