SEGMENTATION FAULT

[Douglas Alves]

I'm using Hoary.
I haven't made any system update, but I before RHIDE's segfault I had
installed OOo2 to compare it with the 1.1 which I still keep.

The segfault happens with no other application running/having-run.

I've never heard/used trace: another Linux lesson to study! :)

Thanks very much.

On Sun, 2005-07-10 at 19:31 -0400, Ed Cogburn wrote:
> Some code in your app is trying to access memory it doesn't have permission
> to access.  This can happen for many reasons, its not necessarily a bug in
> rhide, the segfault could be triggered by some library that rhide is
> calling, or perhaps something else is borked in your system that's
> resulting in rhide being passed bogus information from the operating
> system.
> 
> Hoary or Breezy?
> 
> Any system changes/updates since the last time you ran rhide?
> 
> Try using strace or ltrace with the -S option to trace what the program is
> doing and find out what system call its issuing that causes the segfault. 
> This might give you a clue, or at least its something you can provide with
> a bug report.
> 
> Segfaults are the worst kind of problem on Linux since the error rarely
> actually helps you figure out the problem.  I'm on Breezy and have several
> KDE apps segfaulting without any meaningful clue as to what the problem is. 
> Sigh.
> 
> 
>