Hi,
today in yum update show this problem:
Segmentation fault
Any idea about this problem?
On 9/14/07, Daniel Bruno danielbrunos@gmail.com wrote:
Hi,
today in yum update show this problem:
Segmentation fault
Any idea about this problem?
Could you provide us a bit more detail please? Which version of centos are you using, and on which architecture? Do you have any additional repositories configured (rpmforge, ATrpms, etc) Have you been messing with python recently? How long has it been since you've rebooted (more than 2 kernel updates)? etc.
Centos 5, i386 I dont have additional repositories. The system was installed recently..
On 9/14/07, Jim Perrin jperrin@gmail.com wrote:
On 9/14/07, Daniel Bruno danielbrunos@gmail.com wrote:
Hi,
today in yum update show this problem:
Segmentation fault
Any idea about this problem?
Could you provide us a bit more detail please? Which version of centos are you using, and on which architecture? Do you have any additional repositories configured (rpmforge, ATrpms, etc) Have you been messing with python recently? How long has it been since you've rebooted (more than 2 kernel updates)? etc.
-- During times of universal deceit, telling the truth becomes a revolutionary act. George Orwell _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
On 9/14/07, Daniel Bruno danielbrunos@gmail.com wrote:
Centos 5, i386 I dont have additional repositories. The system was installed recently..
And the rest of the information? Also, run yum in debug mode and see what it says.
yum -d6 update
I rebooted yesterday. Have 2 kernels I haven't messed with python recently
On 9/14/07, Jim Perrin jperrin@gmail.com wrote:
On 9/14/07, Daniel Bruno danielbrunos@gmail.com wrote:
Hi,
today in yum update show this problem:
Segmentation fault
Any idea about this problem?
Could you provide us a bit more detail please? Which version of centos are you using, and on which architecture? Do you have any additional repositories configured (rpmforge, ATrpms, etc) Have you been messing with python recently? How long has it been since you've rebooted (more than 2 kernel updates)? etc.
-- During times of universal deceit, telling the truth becomes a revolutionary act. George Orwell _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
On 9/14/07, Daniel Bruno danielbrunos@gmail.com wrote:
I rebooted yesterday. Have 2 kernels I haven't messed with python recently
Okay, you have to help us help you. I can't see your screen from here. Please provide information we'd consider useful.
Dear Daniel,
I can right now define "Segmentation Fault"
When a process is trying to exceed the memroy location of what allocated to it, we normally face in this case "segmentation fault".
I face this problem, when i run rrd-analyzer.php(jffnms) manually.
Regards,
Umair Shakil ETD
On 9/15/07, Daniel Bruno danielbrunos@gmail.com wrote:
Hi,
today in yum update show this problem:
Segmentation fault
Any idea about this problem?
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
umair shakil wrote:
I can right now define "Segmentation Fault" When a process is trying to exceed the memroy location of what allocated to it, we normally face in this case "segmentation fault".
That is not correct. a segfault is when a process will try to access memory that its not authorised to, eg. trying to write to memory marked read-only is the classic case.
Dear Karanbir,
Please can u please explain me that "trying to exceed the memroy" or "try to gain the memory not authorized" is there making any difference......
OR please i suppose my mistake was "not using google exact defination" :)
Regards,
Umair Shakil
On 9/17/07, Karanbir Singh mail-lists@karan.org wrote:
umair shakil wrote:
I can right now define "Segmentation Fault" When a process is trying to exceed the memroy location of what allocated to it, we normally face in this case "segmentation fault".
That is not correct. a segfault is when a process will try to access memory that its not authorised to, eg. trying to write to memory marked read-only is the classic case.
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
On Tue, Sep 18, 2007 at 08:40:03AM +0500, umair shakil wrote:
Dear Karanbir, Please can u please explain me that "trying to exceed the memroy" or "try to gain the memory not authorized" is there making any difference......
Yes. It necessarily isn't a matter of amount, as implied by "trying to exceed". It's a matter of *where*. Of course, if you try to exceed the memory you've allocated, that will often fall outside of the allowed bounds. And that is indeed a typical reason for this type of crash.
Dear Matthew,
Well, what should be the solution of this problem???? when i faced the problem reinstall the application, but havenot find the exact solution???
Regards,
Umair Shakil ETD
On 9/18/07, Matthew Miller mattdm@mattdm.org wrote:
On Tue, Sep 18, 2007 at 08:40:03AM +0500, umair shakil wrote:
Dear Karanbir, Please can u please explain me that "trying to exceed the memroy" or
"try to
gain the memory not authorized" is there making any difference......
Yes. It necessarily isn't a matter of amount, as implied by "trying to exceed". It's a matter of *where*. Of course, if you try to exceed the memory you've allocated, that will often fall outside of the allowed bounds. And that is indeed a typical reason for this type of crash.
-- Matthew Miller mattdm@mattdm.org http://mattdm.org/ Boston University Linux ------> http://linux.bu.edu/ _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
umair shakil wrote:
Well, what should be the solution of this problem???? when i faced the problem reinstall the application, but havenot find the exact solution???
firstly, I am going to ignore all your emails from here on that are top posted.
secondly, file a bugreport with a reproducer case at http://bugs.centos.org/ and we can look see. I personally have no such issue on any of my machines.