Re: Segmentation fault in Chromium

[Marco M.]

Am 02.10.2023 um 13:16:24 Uhr schrieb Richmond:

> I received a segmentation fault from chromium. Would it be logged
> anywhere?

Install gdb and run it with that to get more information.

Re: Segmentation fault in top -b1 -hc

[Curt]

On 2017-05-09, Bob McGowan  wrote:
>>
> I just tried the OP's command line and got the following error:
>
> $ top -b1 -hc
>   procps-ng 3.3.12
> Usage:
>   top -hv | -bcHiOSs -d secs -n max -u|U user -p pid(s) -o field -w [cols]
>
> I can say with assurance that I have not manually installed anything
> related to procps or top.
>
> And the policy for procps says:
>
> $ apt-cache policy procps  
> procps:
>   Installed: 2:3.3.12-3
>   Candidate: 2:3.3.12-3
>   Version table:
>
> Those version numbers match the numeric part of the 'top' output.
>
> Could it be that Debian has just dropped the '-ng' from the name?
>

I'm reading that in 2011 Debian, Fedora and openSUSE forked procps (which became
'procps-ng'-- next generation). I guess the package has gone back to being
called procps (or something)?

https://gitlab.com/procps-ng/procps/wikis/faq



-- 
"It might be a vision--of a shell, of a wheelbarrow, of a fairy kingdom on the
far side of the hedge; or it might be the glory of speed; no one knew." --Mrs.
Ramsay, speculating on why her little daughter might be dashing about, in "To
the Lighthouse," by Virginia Woolf.

Re: Segmentation fault in top -b1 -hc

[Bob McGowan]

On 05/08/2017 03:28 AM, to...@tuxteam.de wrote:
> On Mon, May 08, 2017 at 11:46:13AM +0200, Peter Ludikovsky wrote:
> > On 05/08/2017 11:19 AM, Valentin Bajrami wrote:
> >> Hi,
> >>
> >> There is a segmentation fault when top is used as follow
> >>
> >> top -b1 -hc
> >>
> >> I think the args are not parsed properly.  The version used is:
> >> procps-ng version 3.3.10
> >>
> >> --
> >> Met vriendelijke groet,
> >>
> >> Valentin Bajrami
>
> > There's no package procps-ng [0].
>
> Indeed. There seems to be one props-ng floating around, but it doesn't
> come from Debian's official repos.
>
> To find out where that package comes from, try
>
>   apt-cache policy procps-ng-3.3.10
>
> (or however that package is really called, you can find that out
> with "aptitude search procps-ng" or something similar).
>
> HTH
> -- tomás
>
I just tried the OP's command line and got the following error:

$ top -b1 -hc
  procps-ng 3.3.12
Usage:
  top -hv | -bcHiOSs -d secs -n max -u|U user -p pid(s) -o field -w [cols]

I can say with assurance that I have not manually installed anything
related to procps or top.

And the policy for procps says:

$ apt-cache policy procps  
procps:
  Installed: 2:3.3.12-3
  Candidate: 2:3.3.12-3
  Version table:

Those version numbers match the numeric part of the 'top' output.

Could it be that Debian has just dropped the '-ng' from the name?

Bob

Re: Segmentation fault in top -b1 -hc

[tomas]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On Mon, May 08, 2017 at 11:46:13AM +0200, Peter Ludikovsky wrote:
> On 05/08/2017 11:19 AM, Valentin Bajrami wrote:
> > Hi,
> > 
> > There is a segmentation fault when top is used as follow
> > 
> > top -b1 -hc
> > 
> > I think the args are not parsed properly.  The version used is:
> > procps-ng version 3.3.10
> > 
> > -- 
> > Met vriendelijke groet,
> > 
> > Valentin Bajrami
> 
> There's no package procps-ng [0].

Indeed. There seems to be one props-ng floating around, but it doesn't
come from Debian's official repos.

To find out where that package comes from, try

  apt-cache policy procps-ng-3.3.10

(or however that package is really called, you can find that out
with "aptitude search procps-ng" or something similar).

HTH
- -- tomás
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEARECAAYFAlkQSFkACgkQBcgs9XrR2kbX3gCfXDWfXzu0pWvamzNf/zhrB+oy
FRoAnArOJblkZjkgdcqayi4spPSu6uMq
=V0kt
-END PGP SIGNATURE-

Re: Segmentation fault in top -b1 -hc

[Peter Ludikovsky]

On 05/08/2017 11:19 AM, Valentin Bajrami wrote:
> Hi,
> 
> There is a segmentation fault when top is used as follow
> 
> top -b1 -hc
> 
> I think the args are not parsed properly.  The version used is:
> procps-ng version 3.3.10
> 
> -- 
> Met vriendelijke groet,
> 
> Valentin Bajrami

There's no package procps-ng [0].

procps is version 3.3.9 in Stable, and 3.3.12 in Testing/Unstable [1].
Update to the current version, and if the problem persists please report
the issue via the reportbug [2][3] utility.

Regards
/peter

[0] https://packages.debian.org/search?keywords=procps-ng
[1] https://packages.debian.org/search?keywords=procps
[2] https://wiki.debian.org/reportbug
[3] https://www.debian.org/Bugs/Reporting



signature.asc
Description: OpenPGP digital signature

Re: segmentation fault when playing videos

[Thomas Schmitt]

Hi,

Christian Hödl wrote:
 [...] vlc [...]
 Program terminated with signal SIGSEGV, Segmentation fault.
 #0  0x7f1726489743 in av_freep () from 
 /usr/lib/x86_64-linux-gnu/libavutil.so.54
 [...] xine [...]
 Program terminated with signal SIGABRT, Aborted.
 #0  0x7f79cd291107 in __GI_raise (sig=sig@entry=6) at
 ../nptl/sysdeps/unix/sysv/linux/raise.c:56
 56    ../nptl/sysdeps/unix/sysv/linux/raise.c: No such file or directory.

Both look like (software) memory corruption.
Usually caused by writing over the limits of an allocated
piece of memory or by de-allocating allocated memory twice.

The culprit is often hard to find because the memory management
might need quite some time until it is rotten enough to crash.


 #0  0x7f79cd291107 in __GI_raise (sig=sig@entry=6) at 
 ../nptl/sysdeps/unix/sysv/linux/raise.c:56
 #1  0x7f79cd2924e8 in __GI_abort () at abort.c:89
 #2  0x7f79cd2cf204 in __libc_message (do_abort=do_abort@entry=1,
 fmt=fmt@entry=0x7f79cd3c1fe0 *** Error in `%s': %s: 0x%s ***\n) at
 ../sysdeps/posix/libc_fatal.c:175

Underneath xine, libc seems to have noticed the problem
before it lead to a crash. I guess it issued a message 
and then deliberately threw signal 6 = SIGABRT (man 7 signal).


A standard tool to catch the culprit is valgrind.
Often awfully slow. So it might produce its own problems with
video display.
Nevertheless it might find the first memory abuse which starts
the whole mess.

  valgrind xine ...xine.options... 21 | tee -i /tmp/valgrind_xine.log

In any case the output will be useful if you file a bug report.


Have a nice day :)

Thomas

Re: Segmentation fault with iceape, etc.

[Paul E Condon]

On 20110413_202225, Javier Vasquez wrote:
 On Wed, Apr 13, 2011 at 8:02 PM, Don J d...@noark.net wrote:
  For a week or more, I've been having problems with iceape and a few
  other programs.  As far as I can see, they get a segmentation fault
  and just disappear.  From the debugging and back traces that I've
  done, it appears that I may be missing or have corrupted files
  relating to Gtk and GLib.  Unfortunately, I'm not savvy enough to
  decipher the information and correct the problem.  I could use a
  little assistance with this.
 
  I am running KDE and wheezy with the updated kernel 2.6.38-2-686 #1
  SMP.  The new kernel had no effect on the problem.  Wheezy is up to
  date.  iceape version is 2.0.13-1
 
  Some of the operations which cause a seg fault include trying to send
  email with iceape (always), sometimes opening a particular web page
  will do it, and it appears the acroread will always do it (while other
  pdf readers will not).  At times, gmail started from the iceape web
  browser will also fault.  I'm only able to send email via using Google
  Chrome to start gmail.
 
  I installed iceape-dbg and followed the directions in the file at
  /usr/share/bug/iceape-dbg/presubj
 
  Starting iceape in safe mode with iceape -safe-more command line
  resulted in segmentation fault; following the suggestion to use the
  MOZILLA_DISABLE_PLUGINS=1 resulted in many warning and critical as
  you can see in the following screen capture:
 
  don@kali:~$ iceape -safe-mode
  Segmentation fault
  don@kali:~$ MOZILLA_DISABLE_PLUGINS=1 iceape
 
  (iceape-bin:3097): Gtk-WARNING **: Error loading theme icon
  'gtk-go-back-ltr' for stock: Icon 'gtk-go-back-ltr' not present in
  theme
 
  (iceape-bin:3097): GLib-GObject-CRITICAL **: g_object_unref: assertion
  `G_IS_OBJECT (object)' failed
 
  (iceape-bin:3097): Gtk-CRITICAL **: gtk_default_render_icon: assertion
  `base_pixbuf != NULL' failed
 
  (iceape-bin:3097): Gtk-CRITICAL **: IA__gtk_style_render_icon:
  assertion `pixbuf != NULL' failed
 
  (iceape-bin:3097): GLib-GObject-CRITICAL **: g_object_ref: assertion
  `G_IS_OBJECT (object)' failed
 
  (iceape-bin:3097): Gtk-WARNING **: Error loading theme icon
  'gtk-go-forward-ltr' for stock: Icon 'gtk-go-forward-ltr' not present
  in theme
 
  (iceape-bin:3097): GLib-GObject-CRITICAL **: g_object_unref: assertion
  `G_IS_OBJECT (object)' failed
 
  (iceape-bin:3097): Gtk-CRITICAL **: gtk_default_render_icon: assertion
  `base_pixbuf != NULL' failed
 
  (iceape-bin:3097): Gtk-CRITICAL **: IA__gtk_style_render_icon:
  assertion `pixbuf != NULL' failed
 
  (iceape-bin:3097): GLib-GObject-CRITICAL **: g_object_ref: assertion
  `G_IS_OBJECT (object)' failed
 
  (iceape-bin:3097): Gtk-WARNING **: Error loading theme icon
  'gtk-go-forward-ltr' for stock: Icon 'gtk-go-forward-ltr' not present
  in theme
 
  (iceape-bin:3097): GLib-GObject-CRITICAL **: g_object_unref: assertion
  `G_IS_OBJECT (object)' failed
 
  (iceape-bin:3097): Gtk-CRITICAL **: gtk_default_render_icon: assertion
  `base_pixbuf != NULL' failed
 
  (iceape-bin:3097): Gtk-CRITICAL **: IA__gtk_style_render_icon:
  assertion `pixbuf != NULL' failed
 
  (iceape-bin:3097): GLib-GObject-CRITICAL **: g_object_ref: assertion
  `G_IS_OBJECT (object)' failed
 
  (iceape-bin:3097): GLib-GObject-CRITICAL **: g_object_unref: assertion
  `G_IS_OBJECT (object)' failed
 
  (iceape-bin:3097): GLib-GObject-CRITICAL **: g_object_unref: assertion
  `G_IS_OBJECT (object)' failed
 
  (iceape-bin:3097): Gtk-WARNING **: Error loading theme icon
  'gtk-go-forward-ltr' for stock: Icon 'gtk-go-forward-ltr' not present
  in theme
 
  (iceape-bin:3097): GLib-GObject-CRITICAL **: g_object_unref: assertion
  `G_IS_OBJECT (object)' failed
 
  (iceape-bin:3097): Gtk-CRITICAL **: gtk_default_render_icon: assertion
  `base_pixbuf != NULL' failed
 
  (iceape-bin:3097): Gtk-CRITICAL **: IA__gtk_style_render_icon:
  assertion `pixbuf != NULL' failed
 
  (iceape-bin:3097): GLib-GObject-CRITICAL **: g_object_ref: assertion
  `G_IS_OBJECT (object)' failed
  Segmentation fault
  don@kali:~$
 
  I also ran gdb using the command line iceape -g which resulted in
  many lines and eventual segmentation fault.  A bt was also done per
  instructions. I have this in a file if it would help diagnosing my
  problem, but I have a feeling that the above information may be
  adequate for someone to tell me if I am missing files or something.
 
  I also tried installing firefox and it too bombs out the same way as
  iceape, so my suspicion is iceape is OK and it is external file(s).
 
  Can someone interpret the warnings and critical stuff for me?  I'm not
  a newbie, but I have little experience in this area.
 
  I do have two other problems that has recently popped up, and I do not
  know if they are related to this problem or not, but I'll mention just
  in case it should give any more clues:
  (1) iceape, when closed by either the X in upper right corner of KDE
  or thru file-exit, continues to 

Re: Segmentation fault with iceape, etc.

[Javier Vasquez]

On Thu, Apr 14, 2011 at 6:41 AM, Paul E Condon
pecon...@mesanetworks.net wrote:
 On 20110413_202225, Javier Vasquez wrote:
 On Wed, Apr 13, 2011 at 8:02 PM, Don J d...@noark.net wrote:
  For a week or more, I've been having problems with iceape and a few
  other programs.  As far as I can see, they get a segmentation fault
  and just disappear.  From the debugging and back traces that I've
  done, it appears that I may be missing or have corrupted files
  relating to Gtk and GLib.  Unfortunately, I'm not savvy enough to
  decipher the information and correct the problem.  I could use a
  little assistance with this.
 
  I am running KDE and wheezy with the updated kernel 2.6.38-2-686 #1
  SMP.  The new kernel had no effect on the problem.  Wheezy is up to
  date.  iceape version is 2.0.13-1
 
  Some of the operations which cause a seg fault include trying to send
  email with iceape (always), sometimes opening a particular web page
  will do it, and it appears the acroread will always do it (while other
  pdf readers will not).  At times, gmail started from the iceape web
  browser will also fault.  I'm only able to send email via using Google
  Chrome to start gmail.
 
  I installed iceape-dbg and followed the directions in the file at
  /usr/share/bug/iceape-dbg/presubj
 
  Starting iceape in safe mode with iceape -safe-more command line
  resulted in segmentation fault; following the suggestion to use the
  MOZILLA_DISABLE_PLUGINS=1 resulted in many warning and critical as
  you can see in the following screen capture:
 
  don@kali:~$ iceape -safe-mode
  Segmentation fault
  don@kali:~$ MOZILLA_DISABLE_PLUGINS=1 iceape
 
  (iceape-bin:3097): Gtk-WARNING **: Error loading theme icon
  'gtk-go-back-ltr' for stock: Icon 'gtk-go-back-ltr' not present in
  theme
 
  (iceape-bin:3097): GLib-GObject-CRITICAL **: g_object_unref: assertion
  `G_IS_OBJECT (object)' failed
 
  (iceape-bin:3097): Gtk-CRITICAL **: gtk_default_render_icon: assertion
  `base_pixbuf != NULL' failed
 
  (iceape-bin:3097): Gtk-CRITICAL **: IA__gtk_style_render_icon:
  assertion `pixbuf != NULL' failed
 
  (iceape-bin:3097): GLib-GObject-CRITICAL **: g_object_ref: assertion
  `G_IS_OBJECT (object)' failed
 
  (iceape-bin:3097): Gtk-WARNING **: Error loading theme icon
  'gtk-go-forward-ltr' for stock: Icon 'gtk-go-forward-ltr' not present
  in theme
 
  (iceape-bin:3097): GLib-GObject-CRITICAL **: g_object_unref: assertion
  `G_IS_OBJECT (object)' failed
 
  (iceape-bin:3097): Gtk-CRITICAL **: gtk_default_render_icon: assertion
  `base_pixbuf != NULL' failed
 
  (iceape-bin:3097): Gtk-CRITICAL **: IA__gtk_style_render_icon:
  assertion `pixbuf != NULL' failed
 
  (iceape-bin:3097): GLib-GObject-CRITICAL **: g_object_ref: assertion
  `G_IS_OBJECT (object)' failed
 
  (iceape-bin:3097): Gtk-WARNING **: Error loading theme icon
  'gtk-go-forward-ltr' for stock: Icon 'gtk-go-forward-ltr' not present
  in theme
 
  (iceape-bin:3097): GLib-GObject-CRITICAL **: g_object_unref: assertion
  `G_IS_OBJECT (object)' failed
 
  (iceape-bin:3097): Gtk-CRITICAL **: gtk_default_render_icon: assertion
  `base_pixbuf != NULL' failed
 
  (iceape-bin:3097): Gtk-CRITICAL **: IA__gtk_style_render_icon:
  assertion `pixbuf != NULL' failed
 
  (iceape-bin:3097): GLib-GObject-CRITICAL **: g_object_ref: assertion
  `G_IS_OBJECT (object)' failed
 
  (iceape-bin:3097): GLib-GObject-CRITICAL **: g_object_unref: assertion
  `G_IS_OBJECT (object)' failed
 
  (iceape-bin:3097): GLib-GObject-CRITICAL **: g_object_unref: assertion
  `G_IS_OBJECT (object)' failed
 
  (iceape-bin:3097): Gtk-WARNING **: Error loading theme icon
  'gtk-go-forward-ltr' for stock: Icon 'gtk-go-forward-ltr' not present
  in theme
 
  (iceape-bin:3097): GLib-GObject-CRITICAL **: g_object_unref: assertion
  `G_IS_OBJECT (object)' failed
 
  (iceape-bin:3097): Gtk-CRITICAL **: gtk_default_render_icon: assertion
  `base_pixbuf != NULL' failed
 
  (iceape-bin:3097): Gtk-CRITICAL **: IA__gtk_style_render_icon:
  assertion `pixbuf != NULL' failed
 
  (iceape-bin:3097): GLib-GObject-CRITICAL **: g_object_ref: assertion
  `G_IS_OBJECT (object)' failed
  Segmentation fault
  don@kali:~$
 
  I also ran gdb using the command line iceape -g which resulted in
  many lines and eventual segmentation fault.  A bt was also done per
  instructions. I have this in a file if it would help diagnosing my
  problem, but I have a feeling that the above information may be
  adequate for someone to tell me if I am missing files or something.
 
  I also tried installing firefox and it too bombs out the same way as
  iceape, so my suspicion is iceape is OK and it is external file(s).
 
  Can someone interpret the warnings and critical stuff for me?  I'm not
  a newbie, but I have little experience in this area.
 
  I do have two other problems that has recently popped up, and I do not
  know if they are related to this problem or not, but I'll mention just
  in case it should give any more clues:
  (1) iceape, when closed 

Re: Segmentation fault with iceape, etc.

[Javier Vasquez]

On Wed, Apr 13, 2011 at 8:02 PM, Don J d...@noark.net wrote:
 For a week or more, I've been having problems with iceape and a few
 other programs.  As far as I can see, they get a segmentation fault
 and just disappear.  From the debugging and back traces that I've
 done, it appears that I may be missing or have corrupted files
 relating to Gtk and GLib.  Unfortunately, I'm not savvy enough to
 decipher the information and correct the problem.  I could use a
 little assistance with this.

 I am running KDE and wheezy with the updated kernel 2.6.38-2-686 #1
 SMP.  The new kernel had no effect on the problem.  Wheezy is up to
 date.  iceape version is 2.0.13-1

 Some of the operations which cause a seg fault include trying to send
 email with iceape (always), sometimes opening a particular web page
 will do it, and it appears the acroread will always do it (while other
 pdf readers will not).  At times, gmail started from the iceape web
 browser will also fault.  I'm only able to send email via using Google
 Chrome to start gmail.

 I installed iceape-dbg and followed the directions in the file at
 /usr/share/bug/iceape-dbg/presubj

 Starting iceape in safe mode with iceape -safe-more command line
 resulted in segmentation fault; following the suggestion to use the
 MOZILLA_DISABLE_PLUGINS=1 resulted in many warning and critical as
 you can see in the following screen capture:

 don@kali:~$ iceape -safe-mode
 Segmentation fault
 don@kali:~$ MOZILLA_DISABLE_PLUGINS=1 iceape

 (iceape-bin:3097): Gtk-WARNING **: Error loading theme icon
 'gtk-go-back-ltr' for stock: Icon 'gtk-go-back-ltr' not present in
 theme

 (iceape-bin:3097): GLib-GObject-CRITICAL **: g_object_unref: assertion
 `G_IS_OBJECT (object)' failed

 (iceape-bin:3097): Gtk-CRITICAL **: gtk_default_render_icon: assertion
 `base_pixbuf != NULL' failed

 (iceape-bin:3097): Gtk-CRITICAL **: IA__gtk_style_render_icon:
 assertion `pixbuf != NULL' failed

 (iceape-bin:3097): GLib-GObject-CRITICAL **: g_object_ref: assertion
 `G_IS_OBJECT (object)' failed

 (iceape-bin:3097): Gtk-WARNING **: Error loading theme icon
 'gtk-go-forward-ltr' for stock: Icon 'gtk-go-forward-ltr' not present
 in theme

 (iceape-bin:3097): GLib-GObject-CRITICAL **: g_object_unref: assertion
 `G_IS_OBJECT (object)' failed

 (iceape-bin:3097): Gtk-CRITICAL **: gtk_default_render_icon: assertion
 `base_pixbuf != NULL' failed

 (iceape-bin:3097): Gtk-CRITICAL **: IA__gtk_style_render_icon:
 assertion `pixbuf != NULL' failed

 (iceape-bin:3097): GLib-GObject-CRITICAL **: g_object_ref: assertion
 `G_IS_OBJECT (object)' failed

 (iceape-bin:3097): Gtk-WARNING **: Error loading theme icon
 'gtk-go-forward-ltr' for stock: Icon 'gtk-go-forward-ltr' not present
 in theme

 (iceape-bin:3097): GLib-GObject-CRITICAL **: g_object_unref: assertion
 `G_IS_OBJECT (object)' failed

 (iceape-bin:3097): Gtk-CRITICAL **: gtk_default_render_icon: assertion
 `base_pixbuf != NULL' failed

 (iceape-bin:3097): Gtk-CRITICAL **: IA__gtk_style_render_icon:
 assertion `pixbuf != NULL' failed

 (iceape-bin:3097): GLib-GObject-CRITICAL **: g_object_ref: assertion
 `G_IS_OBJECT (object)' failed

 (iceape-bin:3097): GLib-GObject-CRITICAL **: g_object_unref: assertion
 `G_IS_OBJECT (object)' failed

 (iceape-bin:3097): GLib-GObject-CRITICAL **: g_object_unref: assertion
 `G_IS_OBJECT (object)' failed

 (iceape-bin:3097): Gtk-WARNING **: Error loading theme icon
 'gtk-go-forward-ltr' for stock: Icon 'gtk-go-forward-ltr' not present
 in theme

 (iceape-bin:3097): GLib-GObject-CRITICAL **: g_object_unref: assertion
 `G_IS_OBJECT (object)' failed

 (iceape-bin:3097): Gtk-CRITICAL **: gtk_default_render_icon: assertion
 `base_pixbuf != NULL' failed

 (iceape-bin:3097): Gtk-CRITICAL **: IA__gtk_style_render_icon:
 assertion `pixbuf != NULL' failed

 (iceape-bin:3097): GLib-GObject-CRITICAL **: g_object_ref: assertion
 `G_IS_OBJECT (object)' failed
 Segmentation fault
 don@kali:~$

 I also ran gdb using the command line iceape -g which resulted in
 many lines and eventual segmentation fault.  A bt was also done per
 instructions. I have this in a file if it would help diagnosing my
 problem, but I have a feeling that the above information may be
 adequate for someone to tell me if I am missing files or something.

 I also tried installing firefox and it too bombs out the same way as
 iceape, so my suspicion is iceape is OK and it is external file(s).

 Can someone interpret the warnings and critical stuff for me?  I'm not
 a newbie, but I have little experience in this area.

 I do have two other problems that has recently popped up, and I do not
 know if they are related to this problem or not, but I'll mention just
 in case it should give any more clues:
 (1) iceape, when closed by either the X in upper right corner of KDE
 or thru file-exit, continues to operate.  I have to kill the process
 in order to restart iceape several minutes later.
 (2) the icons on my desktop do not maintain their position if
 rebooted, and 

Re: segmentation fault with NVIDIA 32bit part

[Sjoerd Hardeman]

lee schreef:
 On Fri, Oct 09, 2009 at 08:45:02AM +0200, Sjoerd Hardeman wrote:
 
 My quake3 copy is running fine with the 64-bit nvidia drivers.
 Without having the 32bit compatibility libraries installed? I have
 quake4 and don't know about quake3, but all games that aren't 64bit
 seem to need the 32bit drivers.
 The nivida driver seems to provide it's own libraries that replace the
 ones that come from somewhere else (with xorg, I guess).
 
 What's quake3 using? SDL? You could check the quake3 executable to see
 what it is (like: file quake3).
/usr/local/games/quake3/quake3.x86: ELF 32-bit LSB executable, Intel
80386, version 1 (GNU/Linux), dynamically linked (uses shared libs), for
GNU/Linux 2.0.0, stripped
 
 Quake4 uses SDL and tries to load libGL.so.1, which it currently can't
 because it needs the 32bit version of that.
I have a /usr/lib32/libGL.so.1 from the ia32-libs package
apt-file search libGL.so.1
ia32-libs: /usr/lib32/libGL.so.1
ia32-libs: /usr/lib32/libGL.so.1.2
Yet, installing nvidia-glx-ia32 might also provide you with the
necessary file:
nvidia-glx-ia32: /emul/ia32-linux/usr/lib/libGL.so.1
nvidia-glx-ia32: /emul/ia32-linux/usr/lib/libGL.so.173.14.09
My understanding, though is that nvidia-glx-ia32 is for 32-bit xserver
environments (eg. xfree86).

I do not notice any problem with the version of libGL.so.1 I use. quake3
does something like 90 fps at the highest quality on my laptop.
Openarena doesn't do much better..
 Anyway, I've seen a forum post on the nvidia website saying that
 you're supposed to use the nvidia driver that comes in your
 distribution because it's supposed to be better integrated than the
 installer provided by nvidia.
 
 So how do I solve the dependency problems with that?
Just install nvidia-kernel-source, nvidia-kernel-common and nvidia-glx.
Ignore the dependency problem of nvidia-glx for now. Continue doing a
module-assistant prepare, m-a auto-install nvidia. That gives you a
compiled kernel module, which will be automatically installed. At this
moment the dependencies for nvidia-glx will be met so it will
automatically be configured as well. Use nvidia as your graphics card
driver in xorg (or use nvidia-settings as a tool to create an xorg for
you) and everything should work. At least, for me that's the case ;)

Sjoerd



signature.asc
Description: OpenPGP digital signature

Re: segmentation fault with NVIDIA 32bit part

[Charles Kroeger]

 today I updated my testing installation. Now the 32bit part of the
 NVIDIA drivers doesn't work anymore

I don't have 64bit strong hardware but it sounds like the problem I have after 
a Linux Kernel is upgraded. 

For Squeeze/Sid I'm showing: 2.6.30-2 (686)

After the upgrade I can expect the 'nvidia' driver to fail. I edit the 
/etc/X11/xorg.conf file replacing 'nvidia' with xorg's 'nv' driver.  This will 
return the 'desktop' minus 3D capabilities. 

As of 10-12 22:52 UTC,  the nvidia-kernel-source is at 185.18.36.-2

When the n-v-source is upgraded, compile it with:

# m-a -t clean,a-i nvidia-kernel-source

Run another apt-get update for the new glx versions  and other apt-get 
dist-upgrade to install them. 

Change the 'xorg.conf file back to 'nvidia' and all is well once more.

Whether any of the above applies to your situation, I cannot say.
-- 
CK


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Re: segmentation fault with NVIDIA 32bit part

[Sjoerd Hardeman]

lee schreef:
  On Wed, Oct 07, 2009 at 01:36:58PM +0200, Sjoerd Hardeman wrote:
  lee schreef:
  On Tue, Oct 06, 2009 at 08:00:52PM -0700, David Fox wrote:
  More to the point, since you have an amd64 system, why bother with
  ia32 components? I don't recall any need for ia32 for nvidia.
  Where do you get a 64bit version of X3? Or X2? Quake? Doom? Tribal
  Trouble? And so on ...
  My quake3 copy is running fine with the 64-bit nvidia drivers.
 
  Without having the 32bit compatibility libraries installed? I have
  quake4 and don't know about quake3, but all games that aren't 64bit
  seem to need the 32bit drivers.
Well, yes. This is what I've installed:
i   nvidia-glx
i   nvidia-kernel-2.6.31
i A nvidia-kernel-common
i   nvidia-kernel-source
And looking at the frame rate I must have *some* hardware acceleration.
Yet, I thought that the opengl support is in separate libraries, and
that nvidia is just a driver. A program does not use drivers as
libraries, is it? Don't you need 32 bit versions of either
libgl1-mesa-dri or libgl1-mesa-glx? Using apt-file, quake3 need a
libGL.so. I have /usr/lib32/libGL.so from the ia32-libs package.

Sjoerd




signature.asc
Description: OpenPGP digital signature

Re: segmentation fault with NVIDIA 32bit part

[lee]

On Fri, Oct 09, 2009 at 08:45:02AM +0200, Sjoerd Hardeman wrote:

   My quake3 copy is running fine with the 64-bit nvidia drivers.
  
   Without having the 32bit compatibility libraries installed? I have
   quake4 and don't know about quake3, but all games that aren't 64bit
   seem to need the 32bit drivers.
 Well, yes. This is what I've installed:
 i   nvidia-glx
 i   nvidia-kernel-2.6.31
 i A nvidia-kernel-common
 i   nvidia-kernel-source
 And looking at the frame rate I must have *some* hardware acceleration.
 Yet, I thought that the opengl support is in separate libraries, and
 that nvidia is just a driver. A program does not use drivers as
 libraries, is it? Don't you need 32 bit versions of either
 libgl1-mesa-dri or libgl1-mesa-glx? Using apt-file, quake3 need a
 libGL.so. I have /usr/lib32/libGL.so from the ia32-libs package.

Well, I don't know exactly how it works. You need a kernel module for
the card, eventually another module for AGP or DRI (or what it was)
depending on your mainboard (I think I have something compiled into
the kernel to support the card) --- but I'm not sure if you still need
that when you have the card in an extended-PCI slot rather than in an
AGP slot.

Besides that, you need some libraries that seem to provide OpenGL
functions --- and that's probably the part relevant for the games: If
they need that, I guess they need those libraries to be 32bit when
they are 32bit and 64bit when they are 64bit because 32bit libraries
don't go together with 64bit applications.

The nivida driver seems to provide it's own libraries that replace the
ones that come from somewhere else (with xorg, I guess).

What's quake3 using? SDL? You could check the quake3 executable to see
what it is (like: file quake3).

Quake4 uses SDL and tries to load libGL.so.1, which it currently can't
because it needs the 32bit version of that.


Anyway, I've seen a forum post on the nvidia website saying that
you're supposed to use the nvidia driver that comes in your
distribution because it's supposed to be better integrated than the
installer provided by nvidia.

So how do I solve the dependency problems with that?


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Re: segmentation fault with NVIDIA 32bit part

[lee]

On Wed, Oct 07, 2009 at 08:01:47AM -0700, David Fox wrote:
 On Tue, Oct 6, 2009 at 9:46 PM, lee l...@yun.yagibdah.de wrote:
 
  Link where? :) I have a 9800GT.
 
 Oops, I forgot the link.
 
 http://en.wikipedia.org/wiki/VDPAU

Thanks!


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Re: segmentation fault with NVIDIA 32bit part

[lee]

On Wed, Oct 07, 2009 at 01:36:58PM +0200, Sjoerd Hardeman wrote:
 lee schreef:
 On Tue, Oct 06, 2009 at 08:00:52PM -0700, David Fox wrote:
 More to the point, since you have an amd64 system, why bother with
 ia32 components? I don't recall any need for ia32 for nvidia.
 
 Where do you get a 64bit version of X3? Or X2? Quake? Doom? Tribal
 Trouble? And so on ...
 
 My quake3 copy is running fine with the 64-bit nvidia drivers.

Without having the 32bit compatibility libraries installed? I have
quake4 and don't know about quake3, but all games that aren't 64bit
seem to need the 32bit drivers.

 Good to know. Thanks

X2 is working great, though (but I haven't played it on amd64, only
x86)--- if you're interested in X3, you might want to start with
X2. Maybe they get X3 fixed at some time. Both games are _very_
similar, which is a good thing. I didn't get very far with X3 yet
because of the crashes and because it's running in slow motion, but it
seems to be a very good successor. After having played X2, I was
waiting like 2-1/2 years for X3 to find out how the story goes on. I
hope they'll also port the others ...


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Re: segmentation fault with NVIDIA 32bit part

[lee]

On Wed, Oct 07, 2009 at 07:57:52AM -0700, David Fox wrote:

 I think I meant that you didn't need ia32 for nvidia. You'll of course
 need it for things that aren't available as 64-bit executables, or not
 available as source. Over here, that is a pretty short list, since I'm
 not into games much :).

Indeed --- it's fine without the 32bit things, but without, the games
won't work. I can wait because the game I want to play (X3) doesn't
work anyway and they need to fix it first. But it bothers me having
things working only 1/2 way.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Re: segmentation fault with NVIDIA 32bit part

[David Fox]

On Tue, Oct 6, 2009 at 9:46 PM, lee l...@yun.yagibdah.de wrote:

 Then there would need to be only two packages: vdpau for those who
 need it, and the rest (which could suggest vdpau which could tell you
 which cards can use it).

Doing that would probably not be possible, given the nature of this
particular component. nvidia's drivers have always had a kernel-space
component and a user-space component (the user-space component is
nvidia-glx, the kernel is nvidia-kernel-source or variations thereof).
Not having nvidia's drivers completely opem makes the process more
complicated, since other drivers (intel, for example) have begun to
put some of their code in the kernel proper, but essentially from the
user's perspective it's a unified driver that exists totally in
userspace.

What complicates the matter further is that the kernel space part of
the driver has to match the kernel you run. If you're on stable or
testing then you might not have new versions of the kernel just
popping up, but if you change the kernel, you have to rebuild the
module. In some respect ubuntu automates this process - and perhaps
debian does as well; I've not actively used nvidia since switching to
intel back in December. But for instance, my virtualbox has a kernel
space part and that gets automatically updated as part of the upgrade
process any time the kernel changes. (And on karmic, new revs of the
kernel are somewhat frequent.)

But in general, separation of components is not uncommon. Sometimes
documentation is separated from the executable, or a development set
is separated from the libraries. That's to save on space, and not
everyone who has a particular library needs the development component
automatically installed.




-- 
thanks for letting me change the magnetic patterns on your hard disk.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Re: segmentation fault with NVIDIA 32bit part

[Sjoerd Hardeman]

lee schreef:

On Tue, Oct 06, 2009 at 08:00:52PM -0700, David Fox wrote:

More to the point, since you have an amd64 system, why bother with
ia32 components? I don't recall any need for ia32 for nvidia.


Where do you get a 64bit version of X3? Or X2? Quake? Doom? Tribal
Trouble? And so on ...
My quake3 copy is running fine with the 64-bit nvidia drivers. I got 
those from sid, by the way, and compiled them for a non-Debian kernel 
using 'm-a a-i nvidia' as suggested in the other thread. It also runs 
openarena which is a far superior opensource clone of quake3.

I already told LGP a couple times that they need to make a 64bit
version of X3 (even before it came out), but they refused and claim
the 32bit version works just fine. But it doesn't work at all, it's
running in slow motion and keeps crashing. For anyone who plans on
buying that game, just don't. It's a nice game, but before they fixed
these problems, it's a waste of money. If they don't fix it soon, they
should take it back ...

Good to know. Thanks

Sjoerd



signature.asc
Description: OpenPGP digital signature

Re: segmentation fault with NVIDIA 32bit part

[David Fox]

On Tue, Oct 6, 2009 at 9:33 PM, lee l...@yun.yagibdah.de wrote:
 On Tue, Oct 06, 2009 at 08:00:52PM -0700, David Fox wrote:

 More to the point, since you have an amd64 system, why bother with
 ia32 components? I don't recall any need for ia32 for nvidia.

 Where do you get a 64bit version of X3? Or X2? Quake? Doom? Tribal
 Trouble? And so on ...

I think I meant that you didn't need ia32 for nvidia. You'll of course
need it for things that aren't available as 64-bit executables, or not
available as source. Over here, that is a pretty short list, since I'm
not into games much :).





-- 
thanks for letting me change the magnetic patterns on your hard disk.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Re: segmentation fault with NVIDIA 32bit part

[David Fox]

On Tue, Oct 6, 2009 at 9:46 PM, lee l...@yun.yagibdah.de wrote:

 Link where? :) I have a 9800GT.

Oops, I forgot the link.

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


 Unfortunately, there's no roll-back option in aptitude ... or is
 there? If there was, there won't be any need to decide between stable,

That would be nice. Installing the previous version (kept in
/var/cache/apt/archives) did it for me. But rollbacks would be good.




-- 
thanks for letting me change the magnetic patterns on your hard disk.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Re: segmentation fault with NVIDIA 32bit part

[thveillon.debian]

lee a wrote :
 On Tue, Oct 06, 2009 at 12:17:53AM +0200, thveillon.debian wrote:
 lee a wrote:
 On Mon, Oct 05, 2009 at 07:41:47PM +0200, thveillon.debian wrote:

 cat:/home/lee# /emul/ia32-linux/usr/lib/libGLcore.so.1
 Segmentation fault
 cat:/home/lee# 
 the ia32-libs got seriously reworked has I understand, you can use the
 Sid version of nvidia's packages, and install the Debian way using
 module-assistant.
 You mean to install an older Debian package that has the nvidia
 drivers? I looked for nvidia packages, but there doesn't seem to be
 one that would compile things for the kernel I'm using. And I don't
 know what module-assistant is.
 No, you said you are using testing (Squeeze), just like I do, so I am
 not advising to install an older package but the current unstable (Sid)
 nvidia packages set that suit your hardware.
 
 Yeah, sorry, I don't keep track of the release names and get confused
 with them. I'm just using testing, it doesn't matter what its current
 name is ...
 
 The minimum you should have would be nvidia-kernel-common,
 nvidia-kernel-source (to build the kernel module with module-assistant),
 and after the module is built install also nvidia-glx[-ia32].
 
 Which version of the driver do these contain? Would this compile the
 right things for the kernel I'm using?
 

I currently have 185.18.36-2 from Sid installed, my package list look like :

aptitude search ~S~i~nnvidia

i   nvidia-glx
i   nvidia-glx-ia32
i   nvidia-kernel-2.6.31.2-vanilla64   this is the kernel module built
with module-assistant, you won't find this one in your package manager
i   nvidia-kernel-common
i   nvidia-kernel-source
i   nvidia-libvdpau1
i   nvidia-libvdpau1-ia32
i   nvidia-settings
i   nvidia-xconfig

Off course if you want the Sid version you need Sid main and
non-free in your sources.list, and do package (or rather level)
pinning to prevent a global switch to Sid. In simple words, create a
/etc/apt/apt.conf file (or in /etc/apt/apt.conf.d/), and put in it :

APT::Default-Release testing;

You can also do more fine-grained pinning in /etc/apt/preferences (to
be created) OR /etc/apt/apt.conf.d/00preferences (to be created).
Something like :

Package: *
Pin: release a=unstable
Pin-Priority: 101

Should give you manual control over what's installed from Sid/unstable.
Just google around for apt package pinning

 Why can't I just use the nvidia installer? What's the difference?
 
  If you do that directly it will build the default testing version, if
 you install Sid packages first, you can use m-a to build the Sid
 version, that's what I am using now on my Squeeze amd64 box.
 
 But I'm not using a Debian kernel.

Neither am I, 2.6.31.2 here.

 
 It's working here, I tried the Nvidia (beta) script and it fails even in
 expert mode where you can choose install paths.
 Yeah, the nvidia installer seems to work just fine and puts the
 libraries into the right place. But the libraries are not executable
 anymore without yielding a segmentation fault.
 How do you test this, so that I can reproduce the tests here ?
 
 Well, just run the nvidia installer, it will say that some libraries
 cannot be found. When you look them up, they are available where they
 are supposed to be, but when you execute them, you get segmentation
 faults.
 
 Then run the nvidia installer again, but choose to not install the
 32bit libs this time. That goes through without errors, and the libs
 that caused the problem before are gone.

Nvidia installer complains, then goes on spreading bogus links all over
the place, then the program tries to use 64bits libs in place of 32bits
compat ones and fails. I am not a specialist in Nvidia driver internals,
but it looks like it's seriously out of sync with Debian amd64
development right now.

 I am afraid it's more a problem with the proprietary nature of the
 Nvidia driver. If it sucks big time it will always be in last resort
 Nvidia's fault... Debian doesn't have to be tailored around proprietary
 programs just to meet their needs.
 
 It doesn't help users when things suddenly quit working.

Sure it's frustrating, I hate when Skype or GoogleEarth go boom after
an upgrade, but you've got to put the blame where it belongs. And all
the more when running Testing or Sid, development and testing are what
they are meant for.

 
 The web browsers don't work right anymore either and tend to crash now
 :( Instead of being improved, they got worse. What happened to the
 mozilla that included the email client and irc?

 Well, that's another problem, iceweasel works mostly OK here, maybe
 clean up your extensions/plugins ?
 
 There are way too many to do that --- or is there a list of all the
 packages I'd have to remove for that while somehow keeping the things
 I might want to keep installed and not have them removed due to
 dependencies? I'm not so sure if this is actually another problem
 rather than another symptom of the quality of Debian going down: First
 there isn't a web browser that works right 

Re: segmentation fault with NVIDIA 32bit part

[lee]

On Tue, Oct 06, 2009 at 09:45:58AM +0200, thveillon.debian wrote:

 I currently have 185.18.36-2 from Sid installed, my package list look like :
 
 aptitude search ~S~i~nnvidia
 
 i   nvidia-glx
 i   nvidia-glx-ia32
 i   nvidia-kernel-2.6.31.2-vanilla64   this is the kernel module built
 with module-assistant, you won't find this one in your package manager
 i   nvidia-kernel-common
 i   nvidia-kernel-source
 i   nvidia-libvdpau1
 i   nvidia-libvdpau1-ia32
 i   nvidia-settings
 i   nvidia-xconfig

Thanks!

How did you figure out which packages you need? When I look at the
description for nvidia-glx, it says binary drivers and leaves it
totally unclear which kernel versions it supports. Besides, the
version in testing doesn't even support my graphics card. It must be a
couple years old ...

Then look at the description for nvidia-glx-ia32:


These XFree86 4.0 binary drivers provide optimized hardware
acceleration of OpenGL applications via a direct-rendering X Server.


I'm not on ia32, I'm on amd64. That can't be the right package, and
when you look at the description, nvidia-glx does the same as
nvidia-glx-ia32.


And nvidia-kernel-common:


This package contains files shared between NVIDIA module packages.


For which kernel For which driver version???


nvidia-kernel-source:


This package builds the NVIDIA Xorg binary kernel module needed by
nvidia-glx.


For which kernel For which driver version???


I don't know about vdpaul --- is that included in the nvidia
installer?

You see why I don't want to mess with all that? I've been downloading
the installer from nvidias website and used that ever since I got my
first nvidia card 10 years or so ago. Until now, it has been working
just fine.

Why are the package descriptions so poor, and why can't there just be
one package you install?

 Off course if you want the Sid version you need Sid main and

Since my card isn't even supported in testing, I'd have to get those
packages from unstable. I've tried using packages from unstable a
couple times, but the results haven't been good.

 non-free in your sources.list, and do package (or rather level)
 pinning to prevent a global switch to Sid. In simple words, create a
 /etc/apt/apt.conf file (or in /etc/apt/apt.conf.d/), and put in it :
 
 APT::Default-Release testing;
 
 You can also do more fine-grained pinning in /etc/apt/preferences (to
 be created) OR /etc/apt/apt.conf.d/00preferences (to be created).
 Something like :
 
 Package: *
 Pin: release a=unstable
 Pin-Priority: 101
 
 Should give you manual control over what's installed from Sid/unstable.
 Just google around for apt package pinning

Well, that reminds me of getting an ATI mach32 to work with OS/2
(especially 3.0), and I really don't want to go back to that. That's
why I keep buying nvidia: No problems to get them to work (until now).

Really, it's funny: The ATI mach32 worked with OS/2 3.0 only for so
long, then the driver suddenly quit working for no reason, and you had
to go back and try to install it again. About 60% of the time you
could; when you couldn't, you had to install OS/2 again. Now nvidia
and Debian are almost the same.

And if you ever tried OS/2 with an ATI mach32, you might understand
how tired I am of this.

  Why can't I just use the nvidia installer? What's the difference?
  
   If you do that directly it will build the default testing version, if
  you install Sid packages first, you can use m-a to build the Sid
  version, that's what I am using now on my Squeeze amd64 box.
  
  But I'm not using a Debian kernel.
 
 Neither am I, 2.6.31.2 here.

There doesn't seem to be a newer version of the nvidia driver
available than 190.32. So what's the difference?

 Nvidia installer complains, then goes on spreading bogus links all over
 the place, then the program tries to use 64bits libs in place of 32bits
 compat ones and fails. I am not a specialist in Nvidia driver internals,
 but it looks like it's seriously out of sync with Debian amd64
 development right now.

Maybe that is because you mixed testing with unstable?

  I am afraid it's more a problem with the proprietary nature of the
  Nvidia driver. If it sucks big time it will always be in last resort
  Nvidia's fault... Debian doesn't have to be tailored around proprietary
  programs just to meet their needs.
  
  It doesn't help users when things suddenly quit working.
 
 Sure it's frustrating, I hate when Skype or GoogleEarth go boom after
 an upgrade, but you've got to put the blame where it belongs. And all
 the more when running Testing or Sid, development and testing are what
 they are meant for.

So who is to blame? Obviously Debian changed something that made the
nvidia driver stop working. That is very much like the kernel
developers (or Debian developers, if you want to) making a change that
makes 50% of the harddisks suddenly stop working, and your comment
would be that the kernel (Debian) doesn't have to be tailored around
proprietary hardware 

Re: segmentation fault with NVIDIA 32bit part

[lee]

On Tue, Oct 06, 2009 at 09:45:58AM +0200, thveillon.debian wrote:
 I currently have 185.18.36-2 from Sid installed, my package list look like :
 
 aptitude search ~S~i~nnvidia
 
 i   nvidia-glx
 i   nvidia-glx-ia32
 i   nvidia-kernel-2.6.31.2-vanilla64   this is the kernel module built
 with module-assistant, you won't find this one in your package manager
 i   nvidia-kernel-common
 i   nvidia-kernel-source
 i   nvidia-libvdpau1
 i   nvidia-libvdpau1-ia32
 i   nvidia-settings
 i   nvidia-xconfig

So I wanted to give this a try, with the packages that are in
testing. But nvidia-glx-ia32 conflicts with libc6-ia32, and 95
packages depend on that.

Using packages from unstable probably makes it worse. How did you
solve that?


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Re: segmentation fault with NVIDIA 32bit part

[David Fox]

On Mon, Oct 5, 2009 at 10:27 AM, lee l...@yun.yagibdah.de wrote:

 cat:/home/lee# /emul/ia32-linux/usr/lib/libGLcore.so.1
 Segmentation fault
 cat:/home/lee#

You can't run a library directly.

More to the point, since you have an amd64 system, why bother with
ia32 components? I don't recall any need for ia32 for nvidia. Later
you make a reference to nvidia-glx, and nvidia-glx-ia32 - they say
they have the same functionality, but one is amd64 and the other one
is ia32, for mixed 32  64 bit compatible systems. It's been a while
since I ran debian, but I ran ubuntu 64 bit with their nvidia drivers
(coming from Debian) and I don't recall any dependency on 32 bit
stuff. There was some, but it was basically for things like
googleearth etc.



-- 
thanks for letting me change the magnetic patterns on your hard disk.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Re: segmentation fault with NVIDIA 32bit part

[David Fox]

On Tue, Oct 6, 2009 at 6:59 PM, lee l...@yun.yagibdah.de wrote:

 And nvidia-kernel-common:


 This package contains files shared between NVIDIA module packages.

Common refers essentially to support files., You should install the
package, but it's not dependent on the driver or the version of the
kernel.

 nvidia-kernel-source:


 This package builds the NVIDIA Xorg binary kernel module needed by
 nvidia-glx.

For whatever kernel you have. It's tied to the specific release of the
driver version, whatever that may be from testing/unstable. Since it
is source, after you do a module-assistant auto-install, it'll compile
that driver for the kernel you have. Since you have a non-standard
kernel, there might be problems, but then again there may not be.

 I don't know about vdpaul --- is that included in the nvidia
 installer?

vdpau is something that's special to some higher-end nvidia cards. You
may not need that, depending on what card you have.

The link here [1] itemizes supported cards.


 Why are the package descriptions so poor, and why can't there just be
 one package you install?

It would be nice, but essentially you need three components,
nvidia-glx, nvidia-common and nvidia-kernel-source. The first and
third have to match as far as the driver revision, otherwise you get
nasty messages from X. One of these should autoinstall nvidia-common
since it may be dependent on the other two. But it's been sometime
since I messed with nvidia (now using on board Intel graphics).




 Since my card isn't even supported in testing, I'd have to get those
 packages from unstable. I've tried using packages from unstable a
 couple times, but the results haven't been good.

Using pinning and judicious use of aptitude install package -t
unstable when only necessary should make things easier. There have
been occasions when I needed the nvidia driver from (then) unstable.
This was over a year ago when I was using an nvidia card on an old 32
bit system. Once it worked like a charm, the other time I found that
the driver update had (wrongly) decided to include support for
instructions that my processor did not support (movaps/movups). Turns
out that the driver was compiled this way, and the only recourse to
get it to work was to downgrade the package to the prior version.
Since I now have an amd64 I can put such frustration behind me, but
it's bitten me before several times. (My prior cpu was an Athlon
Tbird/1000 which had some support for mmx/3dnow, but assumptions were
made occasionally that said basically any modern 386 based system
would support these instructions, and support for them only arrived in
later versions of the AMD platform.)

And it was with some other distributions at well.

-- 
thanks for letting me change the magnetic patterns on your hard disk.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Re: segmentation fault with NVIDIA 32bit part

[lee]

On Tue, Oct 06, 2009 at 08:00:52PM -0700, David Fox wrote:
 On Mon, Oct 5, 2009 at 10:27 AM, lee l...@yun.yagibdah.de wrote:
 
  cat:/home/lee# /emul/ia32-linux/usr/lib/libGLcore.so.1
  Segmentation fault
  cat:/home/lee#
 
 You can't run a library directly.

Oh. I thought you could --- some time ago, I was reading an article
somewhere saying that they made it so that libs can be executed so
that the lib would print some version information.

But you're right, other libs report segfaults as well when I try. That
means that there must be some other problem. Maybe I can figure it out
tomorrow.

 More to the point, since you have an amd64 system, why bother with
 ia32 components? I don't recall any need for ia32 for nvidia.

Where do you get a 64bit version of X3? Or X2? Quake? Doom? Tribal
Trouble? And so on ...

I already told LGP a couple times that they need to make a 64bit
version of X3 (even before it came out), but they refused and claim
the 32bit version works just fine. But it doesn't work at all, it's
running in slow motion and keeps crashing. For anyone who plans on
buying that game, just don't. It's a nice game, but before they fixed
these problems, it's a waste of money. If they don't fix it soon, they
should take it back ...

Sure I'd like to turn off 32bit support in the kernel. The nvidia
drivers work without, but drivers alone don't get you very far.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Re: segmentation fault with NVIDIA 32bit part

[lee]

On Tue, Oct 06, 2009 at 08:13:57PM -0700, David Fox wrote:
 On Tue, Oct 6, 2009 at 6:59 PM, lee l...@yun.yagibdah.de wrote:
 
  And nvidia-kernel-common:
 
 
  This package contains files shared between NVIDIA module packages.
 
 Common refers essentially to support files., You should install the
 package, but it's not dependent on the driver or the version of the
 kernel.

Then why doesn't the description say so?

  nvidia-kernel-source:
 
 
  This package builds the NVIDIA Xorg binary kernel module needed by
  nvidia-glx.
 
 For whatever kernel you have. It's tied to the specific release of the
 driver version, whatever that may be from testing/unstable. Since it
 is source, after you do a module-assistant auto-install, it'll compile
 that driver for the kernel you have. Since you have a non-standard
 kernel, there might be problems, but then again there may not be.

Then the description should say so ...

  I don't know about vdpaul --- is that included in the nvidia
  installer?
 
 vdpau is something that's special to some higher-end nvidia cards. You
 may not need that, depending on what card you have.
 
 The link here [1] itemizes supported cards.

Link where? :) I have a 9800GT.

  Why are the package descriptions so poor, and why can't there just be
  one package you install?
 
 It would be nice, but essentially you need three components,
 nvidia-glx, nvidia-common and nvidia-kernel-source.

Then there would need to be only two packages: vdpau for those who
need it, and the rest (which could suggest vdpau which could tell you
which cards can use it).

  Since my card isn't even supported in testing, I'd have to get those
  packages from unstable. I've tried using packages from unstable a
  couple times, but the results haven't been good.
 
 Using pinning and judicious use of aptitude install package -t
 unstable when only necessary should make things easier.

They _should_: That doesn't mean that they do. Aptitude has a nasty
tendency to do things I don't want it to do. Now imagine what would
happen if I tried to install the nvidia packages from unstable, given
that in testing, they already break another package upon which 95
other packages depend. I might end up having to upgrade to unstable to
solve all the dependency problems.

Unfortunately, there's no roll-back option in aptitude ... or is
there? If there was, there won't be any need to decide between stable,
testing, unstable and experimental and you could try whatever
combination might work. Just tell aptitude save this current stage,
then try to find something that works, and if it doesn't just tell
aptitude go back to the saved state.

Are they at least working on that?


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Re: segmentation fault with NVIDIA 32bit part

[thveillon.debian]

lee wrote:
 Hi,
 
 today I updated my testing installation. Now the 32bit part of the
 NVIDIA drivers doesn't work anymore: The installer says it cannot find
 the libraries that are supposed to be in
 /emul/ia32-linux/usr/lib/. However, the libraries are there, but when
 I try to run them, I'm getting a segmentation fault:
 
 
 cat:/home/lee# /emul/ia32-linux/usr/lib/libGLcore.so.1
 Segmentation fault
 cat:/home/lee# 
 
 
 I'm using kernel 2.6.30 and have tried:
 
 
 NVIDIA-Linux-x86_64-185.18.36-pkg2.run
 NVIDIA-Linux-x86_64-190.32-pkg2.run
 
 
 The 64bit part seems to work fine, i. e. I can start the X server and
 everything is working, except 32bit software that needs the 32bit
 stuff.
 
 What could be causing this problem? It was working just fine before
 the update today.
 
 

Hi,

the ia32-libs got seriously reworked has I understand, you can use the
Sid version of nvidia's packages, and install the Debian way using
module-assistant.
It's working here, I tried the Nvidia (beta) script and it fails even in
expert mode where you can choose install paths.

Hope it helps,

Tom


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Re: segmentation fault with NVIDIA 32bit part

[lee]

On Mon, Oct 05, 2009 at 07:41:47PM +0200, thveillon.debian wrote:

  cat:/home/lee# /emul/ia32-linux/usr/lib/libGLcore.so.1
  Segmentation fault
  cat:/home/lee# 
 
 the ia32-libs got seriously reworked has I understand, you can use the
 Sid version of nvidia's packages, and install the Debian way using
 module-assistant.

You mean to install an older Debian package that has the nvidia
drivers? I looked for nvidia packages, but there doesn't seem to be
one that would compile things for the kernel I'm using. And I don't
know what module-assistant is.

 It's working here, I tried the Nvidia (beta) script and it fails even in
 expert mode where you can choose install paths.

Yeah, the nvidia installer seems to work just fine and puts the
libraries into the right place. But the libraries are not executable
anymore without yielding a segmentation fault.

Since it worked before, there must have been some change made in
Debian packages --- but against which one(s) would I file a bug
report?


The web browsers don't work right anymore either and tend to crash now
:( Instead of being improved, they got worse. What happened to the
mozilla that included the email client and irc?


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Re: segmentation fault with NVIDIA 32bit part

[thveillon.debian]

lee a wrote:
 On Mon, Oct 05, 2009 at 07:41:47PM +0200, thveillon.debian wrote:
 
 cat:/home/lee# /emul/ia32-linux/usr/lib/libGLcore.so.1
 Segmentation fault
 cat:/home/lee# 
 the ia32-libs got seriously reworked has I understand, you can use the
 Sid version of nvidia's packages, and install the Debian way using
 module-assistant.
 
 You mean to install an older Debian package that has the nvidia
 drivers? I looked for nvidia packages, but there doesn't seem to be
 one that would compile things for the kernel I'm using. And I don't
 know what module-assistant is.

No, you said you are using testing (Squeeze), just like I do, so I am
not advising to install an older package but the current unstable (Sid)
nvidia packages set that suit your hardware.
The minimum you should have would be nvidia-kernel-common,
nvidia-kernel-source (to build the kernel module with module-assistant),
and after the module is built install also nvidia-glx[-ia32].

module-assistant (abbreviated m-a) is an helper package that can take
care of the module build (and most thinks implied by it). Just use
(after installing the package module-assistant of course) :

m-a a-i nvidia-kernel

as root, or just launch the ncurse interface with:

m-a

Of course man m-a is the place to start.

 If you do that directly it will build the default testing version, if
you install Sid packages first, you can use m-a to build the Sid
version, that's what I am using now on my Squeeze amd64 box.

 It's working here, I tried the Nvidia (beta) script and it fails even in
 expert mode where you can choose install paths.
 
 Yeah, the nvidia installer seems to work just fine and puts the
 libraries into the right place. But the libraries are not executable
 anymore without yielding a segmentation fault.

How do you test this, so that I can reproduce the tests here ?

 Since it worked before, there must have been some change made in
 Debian packages --- but against which one(s) would I file a bug
 report?

I am afraid it's more a problem with the proprietary nature of the
Nvidia driver. If it sucks big time it will always be in last resort
Nvidia's fault... Debian doesn't have to be tailored around proprietary
programs just to meet their needs.

 
 The web browsers don't work right anymore either and tend to crash now
 :( Instead of being improved, they got worse. What happened to the
 mozilla that included the email client and irc?
 

Well, that's another problem, iceweasel works mostly OK here, maybe
clean up your extensions/plugins ?

I think what you are looking for is the iceape program in Debian
jargon, not sure about this since I have never used it.

Tom


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Re: segmentation fault with NVIDIA 32bit part

[lee]

On Tue, Oct 06, 2009 at 12:17:53AM +0200, thveillon.debian wrote:
 lee a wrote:
  On Mon, Oct 05, 2009 at 07:41:47PM +0200, thveillon.debian wrote:
  
  cat:/home/lee# /emul/ia32-linux/usr/lib/libGLcore.so.1
  Segmentation fault
  cat:/home/lee# 
  the ia32-libs got seriously reworked has I understand, you can use the
  Sid version of nvidia's packages, and install the Debian way using
  module-assistant.
  
  You mean to install an older Debian package that has the nvidia
  drivers? I looked for nvidia packages, but there doesn't seem to be
  one that would compile things for the kernel I'm using. And I don't
  know what module-assistant is.
 
 No, you said you are using testing (Squeeze), just like I do, so I am
 not advising to install an older package but the current unstable (Sid)
 nvidia packages set that suit your hardware.

Yeah, sorry, I don't keep track of the release names and get confused
with them. I'm just using testing, it doesn't matter what its current
name is ...

 The minimum you should have would be nvidia-kernel-common,
 nvidia-kernel-source (to build the kernel module with module-assistant),
 and after the module is built install also nvidia-glx[-ia32].

Which version of the driver do these contain? Would this compile the
right things for the kernel I'm using?

Why can't I just use the nvidia installer? What's the difference?

  If you do that directly it will build the default testing version, if
 you install Sid packages first, you can use m-a to build the Sid
 version, that's what I am using now on my Squeeze amd64 box.

But I'm not using a Debian kernel.

  It's working here, I tried the Nvidia (beta) script and it fails even in
  expert mode where you can choose install paths.
  
  Yeah, the nvidia installer seems to work just fine and puts the
  libraries into the right place. But the libraries are not executable
  anymore without yielding a segmentation fault.
 
 How do you test this, so that I can reproduce the tests here ?

Well, just run the nvidia installer, it will say that some libraries
cannot be found. When you look them up, they are available where they
are supposed to be, but when you execute them, you get segmentation
faults.

Then run the nvidia installer again, but choose to not install the
32bit libs this time. That goes through without errors, and the libs
that caused the problem before are gone.

 I am afraid it's more a problem with the proprietary nature of the
 Nvidia driver. If it sucks big time it will always be in last resort
 Nvidia's fault... Debian doesn't have to be tailored around proprietary
 programs just to meet their needs.

It doesn't help users when things suddenly quit working.

  The web browsers don't work right anymore either and tend to crash now
  :( Instead of being improved, they got worse. What happened to the
  mozilla that included the email client and irc?
  
 
 Well, that's another problem, iceweasel works mostly OK here, maybe
 clean up your extensions/plugins ?

There are way too many to do that --- or is there a list of all the
packages I'd have to remove for that while somehow keeping the things
I might want to keep installed and not have them removed due to
dependencies? I'm not so sure if this is actually another problem
rather than another symptom of the quality of Debian going down: First
there isn't a web browser that works right anymore (since quite a
while), then things that used to work just fine for like a decade
(nvidia drivers) suddenly quit working and the web browsers got even
worse at the same time.

 I think what you are looking for is the iceape program in Debian
 jargon, not sure about this since I have never used it.

There doesn't seem to be an iceape package in testing. Perhaps the
developers making mozilla stopped making it, but that leaves Debian
without a working web browser. Neither galeon, nor iceweasel or
firefox (which seems to be the same), let alone konqeror really
work. And when you try to file a bug report, you're told not do it but
to go to ridiculous lengths to figure out what's wrong yourself.

Things used to just work in Debian, but they do that less and
less. That isn't good.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Re: Segmentation fault in dpkg and aptitude

[Daniel Burrows]

On Mon, Jul 20, 2009 at 10:44:42PM -0700, Bill Wohler woh...@newt.com was 
heard to say:
 You hit the nail on the head. I ran memtest86+. The original block of
 memory came out clean. The new Mushkin memory had thousands of errors.
 Never seen that before.
 
 Wonder if that was related to the earlier issues I had with
 aptitude/apt-get/dpkg? Maybe not since I hadn't seen the segmentation
 violation in any of them after running apt-get -f install twice. But
 maybe... Let's see if my workaround works for David K Jackson.

  Glad to hear you found your problem.  Memory errors are pretty random
and I suspect that you just were lucky after you ran apt-get -f install.
In particular, apt tools rely a lot on memory-mapped files with internal
pointers, so they would tend to be hit especially hard by bad RAM sticks.
However, if all the data that the program uses is cached in good RAM,
you should be able to run it without any problems.  That would be my
guess about what was happening.

  Daniel


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Re: Segmentation fault in dpkg and aptitude

[pobega]

 Bill Wohler woh...@newt.com writes:

 I found I was able to run apt-get -f install twice and be able to
 use aptitude to perform package maintenance again.

 However, now I'm finding that Emacs and Firefox (Iceweasel) die with
 segmentation faults at random times. Wonder if I'll get this email
 away...

 Has anyone seen these problems as a result of updating these packages?

 Here's a trimmed excerpt from /var/log/aptitude:

 [...]

I'm sorry if this is not useful, but it sounds to me like your problem is
an anomaly. None of the packages installed/upgrades (besides perhaps
libx11) should be affecting Emacs or Firefox. So the question is, if you
try to reinstall the broken packages, do they work?

Again, I'm sorry if this wasn't useful, but I saw that no one else
responded so I figured I'd at least chime in.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Re: Segmentation fault in dpkg and aptitude

[Bill Wohler]

pob...@fuzzydev.org writes:

 Bill Wohler woh...@newt.com writes:

 I found I was able to run apt-get -f install twice and be able to
 use aptitude to perform package maintenance again.

 However, now I'm finding that Emacs and Firefox (Iceweasel) die with
 segmentation faults at random times. Wonder if I'll get this email
 away...

 Has anyone seen these problems as a result of updating these packages?

 Here's a trimmed excerpt from /var/log/aptitude:

 [...]

 I'm sorry if this is not useful, but it sounds to me like your problem is
 an anomaly. None of the packages installed/upgrades (besides perhaps
 libx11) should be affecting Emacs or Firefox. So the question is, if you
 try to reinstall the broken packages, do they work?

That's worth a shot, thanks. On the other hand, Emacs and Firefox were
still running this morning...

Weird.

-- 
Bill Wohler woh...@newt.com  http://www.newt.com/wohler/  GnuPG ID:610BD9AD


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Re: Segmentation fault in dpkg and aptitude

[pobega]

 pob...@fuzzydev.org writes:

 Bill Wohler woh...@newt.com writes:

 I found I was able to run apt-get -f install twice and be able to
 use aptitude to perform package maintenance again.

 However, now I'm finding that Emacs and Firefox (Iceweasel) die with
 segmentation faults at random times. Wonder if I'll get this email
 away...

 Has anyone seen these problems as a result of updating these packages?

 Here's a trimmed excerpt from /var/log/aptitude:

 [...]

 I'm sorry if this is not useful, but it sounds to me like your problem
 is
 an anomaly. None of the packages installed/upgrades (besides perhaps
 libx11) should be affecting Emacs or Firefox. So the question is, if you
 try to reinstall the broken packages, do they work?

 That's worth a shot, thanks. On the other hand, Emacs and Firefox were
 still running this morning...

 Weird.


The only problem I can see is if a program that runs in the background is
segfaulting and you don't know. I'd check your logs as often as possible.


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Re: Segmentation fault in dpkg and aptitude

[Daniel Burrows]

On Sun, Jul 19, 2009 at 09:48:37PM -0700, Bill Wohler woh...@newt.com was 
heard to say:
 Bill Wohler woh...@newt.com writes:
 
  After making the following changes to pull in sid's bluez 4.0 package in
  a lenny system, I'm now getting segmentation faults when I run dpkg and
  aptitude. Any thoughts on how to recover from this?
 
 I found I was able to run apt-get -f install twice and be able to
 use aptitude to perform package maintenance again.
 
 However, now I'm finding that Emacs and Firefox (Iceweasel) die with
 segmentation faults at random times. Wonder if I'll get this email
 away...

  It sounds like bad memory to me.  Have you tried running a memory
checker?

  Daniel


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Re: Segmentation fault in dpkg and aptitude

[Bill Wohler]

Daniel Burrows dburr...@debian.org writes:

 On Sun, Jul 19, 2009 at 09:48:37PM -0700, Bill Wohler woh...@newt.com was 
 heard to say:
 Bill Wohler woh...@newt.com writes:
 
  After making the following changes to pull in sid's bluez 4.0 package in
  a lenny system, I'm now getting segmentation faults when I run dpkg and
  aptitude. Any thoughts on how to recover from this?
 
 I found I was able to run apt-get -f install twice and be able to
 use aptitude to perform package maintenance again.
 
 However, now I'm finding that Emacs and Firefox (Iceweasel) die with
 segmentation faults at random times. Wonder if I'll get this email
 away...

   It sounds like bad memory to me.  Have you tried running a memory
 checker?

Thanks, Daniel. No I haven't since it hadn't occurred to me: the
machine is new and I just added some good quality Mushkin memory. I'll
try memtester, although the documentation says it won't be able to
test all 8 GB of my memory. Then I'll try memtest86+ when I'm not
using the machine. It's been a long, long time since I've used these.
Any other suggestions?

-- 
Bill Wohler woh...@newt.com  http://www.newt.com/wohler/  GnuPG ID:610BD9AD


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Re: Segmentation fault in dpkg and aptitude

[Mark Allums]

Bill Wohler wrote:

Daniel Burrows dburr...@debian.org writes:


On Sun, Jul 19, 2009 at 09:48:37PM -0700, Bill Wohler woh...@newt.com was 
heard to say:

Bill Wohler woh...@newt.com writes:


After making the following changes to pull in sid's bluez 4.0 package in
a lenny system, I'm now getting segmentation faults when I run dpkg and
aptitude. Any thoughts on how to recover from this?

I found I was able to run apt-get -f install twice and be able to
use aptitude to perform package maintenance again.

However, now I'm finding that Emacs and Firefox (Iceweasel) die with
segmentation faults at random times. Wonder if I'll get this email
away...

  It sounds like bad memory to me.  Have you tried running a memory
checker?


Thanks, Daniel. No I haven't since it hadn't occurred to me: the
machine is new and I just added some good quality Mushkin memory. I'll
try memtester, although the documentation says it won't be able to
test all 8 GB of my memory. Then I'll try memtest86+ when I'm not
using the machine. It's been a long, long time since I've used these.
Any other suggestions?



I was getting segfaults when trying to boot, it was an init script 
running tput.  I ran a reinstall on a few things and it went away.


Mark Allums


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Re: Segmentation fault in dpkg and aptitude

[Bill Wohler]

Bill Wohler woh...@newt.com writes:

 Daniel Burrows dburr...@debian.org writes:

 On Sun, Jul 19, 2009 at 09:48:37PM -0700, Bill Wohler woh...@newt.com was 
 heard to say:
 Bill Wohler woh...@newt.com writes:
 
  After making the following changes to pull in sid's bluez 4.0 package in
  a lenny system, I'm now getting segmentation faults when I run dpkg and
  aptitude. Any thoughts on how to recover from this?
 
 I found I was able to run apt-get -f install twice and be able to
 use aptitude to perform package maintenance again.
 
 However, now I'm finding that Emacs and Firefox (Iceweasel) die with
 segmentation faults at random times. Wonder if I'll get this email
 away...

   It sounds like bad memory to me.  Have you tried running a memory
 checker?

 Thanks, Daniel. No I haven't since it hadn't occurred to me: the
 machine is new and I just added some good quality Mushkin memory. I'll
 try memtester, although the documentation says it won't be able to
 test all 8 GB of my memory. Then I'll try memtest86+ when I'm not
 using the machine. It's been a long, long time since I've used these.
 Any other suggestions?

Daniel,

You hit the nail on the head. I ran memtest86+. The original block of
memory came out clean. The new Mushkin memory had thousands of errors.
Never seen that before.

Wonder if that was related to the earlier issues I had with
aptitude/apt-get/dpkg? Maybe not since I hadn't seen the segmentation
violation in any of them after running apt-get -f install twice. But
maybe... Let's see if my workaround works for David K Jackson.

-- 
Bill Wohler woh...@newt.com  http://www.newt.com/wohler/  GnuPG ID:610BD9AD


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Re: Segmentation fault in dpkg and aptitude

[Bill Wohler]

Bill Wohler woh...@newt.com writes:

 After making the following changes to pull in sid's bluez 4.0 package in
 a lenny system, I'm now getting segmentation faults when I run dpkg and
 aptitude. Any thoughts on how to recover from this?

I found I was able to run apt-get -f install twice and be able to
use aptitude to perform package maintenance again.

However, now I'm finding that Emacs and Firefox (Iceweasel) die with
segmentation faults at random times. Wonder if I'll get this email
away...

Has anyone seen these problems as a result of updating these packages?

 Here's a trimmed excerpt from /var/log/aptitude:

 Aptitude 0.4.11.11: log report
 Sun, Jul 19 2009 12:33:18 -0700

 [INSTALL, DEPENDENCIES] libbluetooth3
 [INSTALL, DEPENDENCIES] libnl1
 [INSTALL] bluez
 [UPGRADE] bluez-utils 3.36-3 - 4.42-2

 Aptitude 0.4.11.11: log report
 Sun, Jul 19 2009 12:51:29 -0700

 [INSTALL, DEPENDENCIES] consolekit
 [INSTALL, DEPENDENCIES] libck-connector0
 [INSTALL, DEPENDENCIES] libpam-ck-connector
 [INSTALL, DEPENDENCIES] libpolkit-dbus2
 [INSTALL, DEPENDENCIES] libpolkit-gnome0
 [INSTALL, DEPENDENCIES] libpolkit-grant2
 [INSTALL, DEPENDENCIES] libpolkit2
 [INSTALL, DEPENDENCIES] libxcb-atom1
 [INSTALL, DEPENDENCIES] libxcb-aux0
 [INSTALL, DEPENDENCIES] libxcb-event1
 [INSTALL, DEPENDENCIES] obex-data-server
 [INSTALL, DEPENDENCIES] policykit
 [INSTALL, DEPENDENCIES] policykit-gnome
 [INSTALL, DEPENDENCIES] python-pyrex
 [REMOVE, DEPENDENCIES] bluez-gnome
 [REMOVE, DEPENDENCIES] libxcb-xlib0
 [REMOVE, DEPENDENCIES] libxcb-xlib0-dev
 [INSTALL] blueman
 [UPGRADE] libstartup-notification0 0.9-1 - 0.10-1
 [UPGRADE] libx11-6 2:1.1.5-2 - 2:1.2.1-1
 [UPGRADE] libx11-dev 2:1.1.5-2 - 2:1.2.1-1
 [UPGRADE] libxcb1 1.1-1.2 - 1.3-2
 [UPGRADE] libxcb1-dev 1.1-1.2 - 1.3-2

-- 
Bill Wohler woh...@newt.com  http://www.newt.com/wohler/  GnuPG ID:610BD9AD


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Re: Segmentation fault when stating aptitude

[Bob Cox]

On Mon, Mar 02, 2009 at 18:26:25 -0500, Jacques Dery (de...@inforco.com) wrote: 

 Thank you for the suggestion but the problem still exists.

 Here is the output
 
 de...@gontran:/var/cache/apt$ sudo rm pkgcache.bin

 de...@gontran:/var/cache/apt$ ls -ails
 total 12
 160066 4 drwxr-xr-x  3 root root 4096 2009-03-02 18:13 .
 160006 4 drwxr-xr-x 10 root root 4096 2009-02-26 06:27 ..
 160073 4 drwxr-xr-x  3 root root 4096 2009-03-02 17:52 archives

 de...@gontran:/var/cache/apt$ sudo aptitude update
 Get:1 http://security.debian.org etch/updates Release.gpg [189B]
 Hit http://security.debian.org etch/updates Release
 Get:2 http://ftp.uk.debian.org etch Release.gpg [386B]
 Hit http://ftp.uk.debian.org etch Release
 Ign http://security.debian.org etch/updates/main Packages/DiffIndex
 Ign http://security.debian.org etch/updates/contrib Packages/DiffIndex
 Ign http://security.debian.org etch/updates/main Sources/DiffIndex
 Ign http://security.debian.org etch/updates/contrib Sources/DiffIndex
 Hit http://security.debian.org etch/updates/main Packages
 Ign http://ftp.uk.debian.org etch/main Packages/DiffIndex
 Hit http://security.debian.org etch/updates/contrib Packages
 Hit http://security.debian.org etch/updates/main Sources
 Hit http://security.debian.org etch/updates/contrib Sources
 Ign http://ftp.uk.debian.org etch/contrib Packages/DiffIndex
 Hit http://ftp.uk.debian.org etch/main Packages
 Hit http://ftp.uk.debian.org etch/contrib Packages
 Get:3 http://http.us.debian.org stable Release.gpg [386B]
 Hit http://http.us.debian.org stable Release
 Ign http://http.us.debian.org stable/main Packages/DiffIndex
 Ign http://http.us.debian.org stable/contrib Packages/DiffIndex
 Ign http://http.us.debian.org stable/non-free Packages/DiffIndex
 Hit http://http.us.debian.org stable/main Packages
 Hit http://http.us.debian.org stable/contrib Packages
 Hit http://http.us.debian.org stable/non-free Packages

I notice that you are getting updates and security updates for etch but
also updates for stable (lenny) with no corresponding security updates.

Are you intentionally mixing etch and lenny using pinning or a
APT::Default-Release setting?  Just a thought.

-- 
Bob Cox.  Stoke Gifford, near Bristol, UK.
Please reply to the list only.  Do NOT send copies directly to me.
Debian on the NSLU2: http://bobcox.com/slug/


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Re: Segmentation fault when stating aptitude

[Jacques Dery]

Thank you for the suggestion but the problem still exists.

Here is the output

de...@gontran:/var/cache/apt$ sudo rm pkgcache.bin

de...@gontran:/var/cache/apt$ ls -ails
total 12
160066 4 drwxr-xr-x  3 root root 4096 2009-03-02 18:13 .
160006 4 drwxr-xr-x 10 root root 4096 2009-02-26 06:27 ..
160073 4 drwxr-xr-x  3 root root 4096 2009-03-02 17:52 archives

de...@gontran:/var/cache/apt$ sudo aptitude update
Get:1 http://security.debian.org etch/updates Release.gpg [189B]
Hit http://security.debian.org etch/updates Release
Get:2 http://ftp.uk.debian.org etch Release.gpg [386B]
Hit http://ftp.uk.debian.org etch Release
Ign http://security.debian.org etch/updates/main Packages/DiffIndex
Ign http://security.debian.org etch/updates/contrib Packages/DiffIndex
Ign http://security.debian.org etch/updates/main Sources/DiffIndex
Ign http://security.debian.org etch/updates/contrib Sources/DiffIndex
Hit http://security.debian.org etch/updates/main Packages
Ign http://ftp.uk.debian.org etch/main Packages/DiffIndex
Hit http://security.debian.org etch/updates/contrib Packages
Hit http://security.debian.org etch/updates/main Sources
Hit http://security.debian.org etch/updates/contrib Sources
Ign http://ftp.uk.debian.org etch/contrib Packages/DiffIndex
Hit http://ftp.uk.debian.org etch/main Packages
Hit http://ftp.uk.debian.org etch/contrib Packages
Get:3 http://http.us.debian.org stable Release.gpg [386B]
Hit http://http.us.debian.org stable Release
Ign http://http.us.debian.org stable/main Packages/DiffIndex
Ign http://http.us.debian.org stable/contrib Packages/DiffIndex
Ign http://http.us.debian.org stable/non-free Packages/DiffIndex
Hit http://http.us.debian.org stable/main Packages
Hit http://http.us.debian.org stable/contrib Packages
Hit http://http.us.debian.org stable/non-free Packages
Fetched 3B in 3s (1B/s)
Segmentation faultsts... 90%



I am not sure what is the next step. Any other way out of this?

Thank you
Jacques


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Re: Segmentation fault when stating aptitude

[Daniel Burrows]

On Sun, Mar 01, 2009 at 11:29:30AM -0500, Jacques Dery de...@inforco.com was 
heard to say:
 I tried running apt-get update and aptitude from the commandline with 
 the same result. I looked at the man page. I tried a few commands 
 without result. I am weary going further because I am playing with root 
 and risk doing more damage on the system.

  I would suggest removing /var/cache/apt/*.bin and seeing if that
helps at all.  (run aptitude update after you do that)

  Daniel


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Re: Segmentation Fault

[Allison Vollmann]

Esse erro está dando na hora da instalação certo? Não é normal, devido 
que esse erro ocorre quando um processo tenta acessar um local da 
memória ao qual não foi alocado para ele, como é na instalação da para 
suspeitar que  deve ter algum problema de hardware, ja passou um teste 
de memória?


A[]'s


Fábio de Sousa escreveu:

Boa tarde, amigos debianos...

Estou tentando instalar o debian lenny, mas o erro também já aconteceu 
com o etch!

Estas são as ultimas quatro linhas do log de erro:

debootstrap: Segmentation fault
debootstrap: ar: can't open' 
./var/cache/apt/archive/libstdc++6_4.3.2.2_i386.deb': no such file or 
directory

debootstrap: zcat: short read
debootstrap: tar: short read

Soluções já tentadas:
1 - Instalar com Cd NetInstall
2 - Instalar com Cd Business
3 - Troquei o Hd por três vezes
4 - Troquei memória
5 - Troquei leitora de CD.

Em todas as situações aparecem erros parecidos, e todos com esta 
mensagem em comum: SEGMENTATION FAULT


Alguém saberia me dizer com resolvo, isso?

Grato,
Fábiocs


--
Seja Livre! Use Linux
De preferência o Debian



--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: segmentation fault but why?

[Florian Kulzer]

On Sat, Jan 12, 2008 at 13:39:12 -0500, chris dunn wrote:
 Running scanimage -L as root (su) yields the correct answer and identifies my 
 scanner.
 
 Running scanimage -L as user yields Segmentation fault only.
 
 Does anyone have a suggestion as to why this might be, and how I can identify 
 the reason for the problem?

Install the strace package if you do not have it already.

Run as the normal user:

strace -f scanimage -L 2scanimage.strace

Then you can check the end of the file scanimage.strace for clues. If
you cannot make sense of it then you can send the output of

tail -n50 scanimage.strace

to this list. (Please do NOT post the entire strace file!)

-- 
Regards,| http://users.icfo.es/Florian.Kulzer
  Florian   |


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: Segmentation fault al hacer un ls en Sarge

[[EMAIL PROTECTED]]

On 8/2/07, Iñaki Baz Castillo [EMAIL PROTECTED] wrote:
 Hola, de repente en un servidor Sarge en producción falla casi todo.
 Doy por hecho que el problema tiene mucho que ver con que ni siquiera
 se puede hacer un ls:

 ~# ls
 Segmentation fault

Recuerdo que en ocasiones se me dañaron comandos como ls por cerrar
mal el sistema operativo o por haber ejecutado un comando enviado por
aquellos que quieren ingresar vía ssh a la fuerza :$, con debsum
detecté los archivos que se corrompieron.

Re: Segmentation fault al hacer un ls en Sarge

[Iñaki Baz Castillo]

El Viernes, 3 de Agosto de 2007, [EMAIL PROTECTED] escribió:
 On 8/2/07, Iñaki Baz Castillo [EMAIL PROTECTED] wrote:
  Hola, de repente en un servidor Sarge en producción falla casi todo.
  Doy por hecho que el problema tiene mucho que ver con que ni siquiera
  se puede hacer un ls:
 
  ~# ls
  Segmentation fault

 Recuerdo que en ocasiones se me dañaron comandos como ls por cerrar
 mal el sistema operativo o por haber ejecutado un comando enviado por
 aquellos que quieren ingresar vía ssh a la fuerza :$, con debsum
 detecté los archivos que se corrompieron.

Vaya, gracias, lo tendré en cuenta para otra ocasión, ahora ya el servidor ha 
sido reemplazado ;)

Gracias.

-- 
Iñaki Baz Castillo

Re: Segmentation fault al hacer un ls en Sarge

[ChEnChO]

El 2/08/07, Iñaki Baz Castillo [EMAIL PROTECTED] escribió:
 Hola, de repente en un servidor Sarge en producción falla casi todo.
 Doy por hecho que el problema tiene mucho que ver con que ni siquiera
 se puede hacer un ls:

 ~# ls
 Segmentation fault


 Recuerdo que una vez me pasó lo mismo en otro equipo, aunque sólo a
 partir de un directorio, y recuerdo que lo corregí borrando algún
 archivo (no lo recuerdo muy bien). Pero claro, ahora la situación es
 mucho más grave, y servicios no pueden escribir en /tmp (tal vez
 porque intentan leer antes...).


 Pego un strace ls:


 /# strace ls
 execve(/bin/ls, [ls], [/* 18 vars */]) = 0
 uname({sys=Linux, node=linux, ...}) = 0
 brk(0)  = 0x805b000
 old_mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS,
 -1, 0) = 0x40017000
 access(/etc/ld.so.nohwcap, F_OK)  = -1 ENOENT (No such file or 
 directory)
 open(/etc/ld.so.preload, O_RDONLY)= -1 ENOENT (No such file or 
 directory)
 open(/etc/ld.so.cache, O_RDONLY)  = 3
 fstat64(3, {st_mode=S_IFREG|0644, st_size=16546, ...}) = 0
 old_mmap(NULL, 16546, PROT_READ, MAP_PRIVATE, 3, 0) = 0x40018000
 close(3)= 0
 access(/etc/ld.so.nohwcap, F_OK)  = -1 ENOENT (No such file or 
 directory)
 open(/lib/tls/librt.so.1, O_RDONLY)   = 3
 read(3, \177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0\220\32..., 512) = 
 512
 fstat64(3, {st_mode=S_IFREG|0644, st_size=22940, ...}) = 0
 old_mmap(NULL, 21588, PROT_READ|PROT_EXEC, MAP_PRIVATE, 3, 0) = 0x4001d000
 old_mmap(0x40022000, 4096, PROT_READ|PROT_WRITE,
 MAP_PRIVATE|MAP_FIXED, 3, 0x5000) = 0x40022000
 close(3)= 0
 access(/etc/ld.so.nohwcap, F_OK)  = -1 ENOENT (No such file or 
 directory)
 open(/lib/libacl.so.1, O_RDONLY)  = 3
 read(3, \177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0\300\24..., 512) = 
 512
 fstat64(3, {st_mode=S_IFREG|0644, st_size=22336, ...}) = 0
 old_mmap(NULL, 25412, PROT_READ|PROT_EXEC, MAP_PRIVATE, 3, 0) = 0x40023000
 old_mmap(0x40029000, 4096, PROT_READ|PROT_WRITE,
 MAP_PRIVATE|MAP_FIXED, 3, 0x5000) = 0x40029000
 close(3)= 0
 access(/etc/ld.so.nohwcap, F_OK)  = -1 ENOENT (No such file or 
 directory)
 open(/lib/tls/libc.so.6, O_RDONLY)= 3
 read(3, \177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0`Z\1\000..., 512) = 
 512
 fstat64(3, {st_mode=S_IFREG|0755, st_size=1254660, ...}) = 0
 old_mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS,
 -1, 0) = 0x4002a000
 old_mmap(NULL, 1264972, PROT_READ|PROT_EXEC, MAP_PRIVATE, 3, 0) = 0x4002b000
 old_mmap(0x40155000, 36864, PROT_READ|PROT_WRITE,
 MAP_PRIVATE|MAP_FIXED, 3, 0x129000) = 0x40155000
 old_mmap(0x4015e000, 7500, PROT_READ|PROT_WRITE,
 MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x4015e000
 close(3)= 0
 access(/etc/ld.so.nohwcap, F_OK)  = -1 ENOENT (No such file or 
 directory)
 open(/lib/tls/libpthread.so.0, O_RDONLY) = 3
 read(3, \177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0pF\0\000..., 512) = 
 512
 fstat64(3, {st_mode=S_IFREG|0755, st_size=78233, ...}) = 0
 old_mmap(NULL, 60772, PROT_READ|PROT_EXEC, MAP_PRIVATE, 3, 0) = 0x4016
 old_mmap(0x4016c000, 4096, PROT_READ|PROT_WRITE,
 MAP_PRIVATE|MAP_FIXED, 3, 0xc000) = 0x4016c000
 old_mmap(0x4016d000, 7524, PROT_READ|PROT_WRITE,
 MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x4016d000
 close(3)= 0
 access(/etc/ld.so.nohwcap, F_OK)  = -1 ENOENT (No such file or 
 directory)
 open(/lib/libattr.so.1, O_RDONLY) = 3
 read(3, \177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0\340\r\0..., 512) = 
 512
 fstat64(3, {st_mode=S_IFREG|0644, st_size=10824, ...}) = 0
 old_mmap(NULL, 13892, PROT_READ|PROT_EXEC, MAP_PRIVATE, 3, 0) = 0x4016f000
 old_mmap(0x40172000, 4096, PROT_READ|PROT_WRITE,
 MAP_PRIVATE|MAP_FIXED, 3, 0x2000) = 0x40172000
 close(3)= 0
 old_mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS,
 -1, 0) = 0x40173000
 set_thread_area({entry_number:-1 - 6, base_addr:0x401732a0,
 limit:1048575, seg_32bit:1, contents:0, read_exec_only:0,
 limit_in_pages:1, seg_not_present:0, useable:1}) = 0
 munmap(0x40018000, 16546)   = 0
 set_tid_address(0x401732e8) = 32513
 rt_sigaction(SIGRTMIN, {0x401645d0, [], SA_SIGINFO}, NULL, 8) = 0
 rt_sigprocmask(SIG_UNBLOCK, [RTMIN], NULL, 8) = 0
 getrlimit(RLIMIT_STACK, {rlim_cur=8192*1024, rlim_max=RLIM_INFINITY}) = 0
 --- SIGSEGV (Segmentation fault) @ 0 (0) ---
 +++ killed by SIGSEGV +++



 ¿Alguna sugerencia? Mil gracias.



 --
 Iñaki Baz Castillo
 [EMAIL PROTECTED]


Si no ha habido actualización de por medio, el problema tiene que ser hardware.

Probaría a pasarle un memtest para ver la ram y/o probar con otro disco duro.

A mi me pasó algo similiar con un servidor y tras muchas pruebas, era
un módulo de ram que había cascado.

Suerte


-- 
... may the source be with you...

Re: Segmentation fault al hacer un ls en Sarge

[Adrià]

On 8/2/07, ChEnChO [EMAIL PROTECTED] wrote:
 El 2/08/07, Iñaki Baz Castillo [EMAIL PROTECTED] escribió:
  Hola, de repente en un servidor Sarge en producción falla casi todo.
  Doy por hecho que el problema tiene mucho que ver con que ni siquiera
  se puede hacer un ls:
 
  ~# ls
  Segmentation fault
 
 
  Recuerdo que una vez me pasó lo mismo en otro equipo, aunque sólo a
  partir de un directorio, y recuerdo que lo corregí borrando algún
  archivo (no lo recuerdo muy bien). Pero claro, ahora la situación es
  mucho más grave, y servicios no pueden escribir en /tmp (tal vez
  porque intentan leer antes...).
 
 
  Pego un strace ls:
 
 
  /# strace ls
  execve(/bin/ls, [ls], [/* 18 vars */]) = 0
  uname({sys=Linux, node=linux, ...}) = 0
  brk(0)  = 0x805b000
  old_mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS,
  -1, 0) = 0x40017000
  access(/etc/ld.so.nohwcap, F_OK)  = -1 ENOENT (No such file or 
  directory)
  open(/etc/ld.so.preload, O_RDONLY)= -1 ENOENT (No such file or 
  directory)
  open(/etc/ld.so.cache, O_RDONLY)  = 3
  fstat64(3, {st_mode=S_IFREG|0644, st_size=16546, ...}) = 0
  old_mmap(NULL, 16546, PROT_READ, MAP_PRIVATE, 3, 0) = 0x40018000
  close(3)= 0
  access(/etc/ld.so.nohwcap, F_OK)  = -1 ENOENT (No such file or 
  directory)
  open(/lib/tls/librt.so.1, O_RDONLY)   = 3
  read(3, \177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0\220\32..., 512) = 
  512
  fstat64(3, {st_mode=S_IFREG|0644, st_size=22940, ...}) = 0
  old_mmap(NULL, 21588, PROT_READ|PROT_EXEC, MAP_PRIVATE, 3, 0) = 0x4001d000
  old_mmap(0x40022000, 4096, PROT_READ|PROT_WRITE,
  MAP_PRIVATE|MAP_FIXED, 3, 0x5000) = 0x40022000
  close(3)= 0
  access(/etc/ld.so.nohwcap, F_OK)  = -1 ENOENT (No such file or 
  directory)
  open(/lib/libacl.so.1, O_RDONLY)  = 3
  read(3, \177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0\300\24..., 512) = 
  512
  fstat64(3, {st_mode=S_IFREG|0644, st_size=22336, ...}) = 0
  old_mmap(NULL, 25412, PROT_READ|PROT_EXEC, MAP_PRIVATE, 3, 0) = 0x40023000
  old_mmap(0x40029000, 4096, PROT_READ|PROT_WRITE,
  MAP_PRIVATE|MAP_FIXED, 3, 0x5000) = 0x40029000
  close(3)= 0
  access(/etc/ld.so.nohwcap, F_OK)  = -1 ENOENT (No such file or 
  directory)
  open(/lib/tls/libc.so.6, O_RDONLY)= 3
  read(3, \177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0`Z\1\000..., 512) 
  = 512
  fstat64(3, {st_mode=S_IFREG|0755, st_size=1254660, ...}) = 0
  old_mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS,
  -1, 0) = 0x4002a000
  old_mmap(NULL, 1264972, PROT_READ|PROT_EXEC, MAP_PRIVATE, 3, 0) = 0x4002b000
  old_mmap(0x40155000, 36864, PROT_READ|PROT_WRITE,
  MAP_PRIVATE|MAP_FIXED, 3, 0x129000) = 0x40155000
  old_mmap(0x4015e000, 7500, PROT_READ|PROT_WRITE,
  MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x4015e000
  close(3)= 0
  access(/etc/ld.so.nohwcap, F_OK)  = -1 ENOENT (No such file or 
  directory)
  open(/lib/tls/libpthread.so.0, O_RDONLY) = 3
  read(3, \177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0pF\0\000..., 512) 
  = 512
  fstat64(3, {st_mode=S_IFREG|0755, st_size=78233, ...}) = 0
  old_mmap(NULL, 60772, PROT_READ|PROT_EXEC, MAP_PRIVATE, 3, 0) = 0x4016
  old_mmap(0x4016c000, 4096, PROT_READ|PROT_WRITE,
  MAP_PRIVATE|MAP_FIXED, 3, 0xc000) = 0x4016c000
  old_mmap(0x4016d000, 7524, PROT_READ|PROT_WRITE,
  MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x4016d000
  close(3)= 0
  access(/etc/ld.so.nohwcap, F_OK)  = -1 ENOENT (No such file or 
  directory)
  open(/lib/libattr.so.1, O_RDONLY) = 3
  read(3, \177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0\340\r\0..., 512) 
  = 512
  fstat64(3, {st_mode=S_IFREG|0644, st_size=10824, ...}) = 0
  old_mmap(NULL, 13892, PROT_READ|PROT_EXEC, MAP_PRIVATE, 3, 0) = 0x4016f000
  old_mmap(0x40172000, 4096, PROT_READ|PROT_WRITE,
  MAP_PRIVATE|MAP_FIXED, 3, 0x2000) = 0x40172000
  close(3)= 0
  old_mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS,
  -1, 0) = 0x40173000
  set_thread_area({entry_number:-1 - 6, base_addr:0x401732a0,
  limit:1048575, seg_32bit:1, contents:0, read_exec_only:0,
  limit_in_pages:1, seg_not_present:0, useable:1}) = 0
  munmap(0x40018000, 16546)   = 0
  set_tid_address(0x401732e8) = 32513
  rt_sigaction(SIGRTMIN, {0x401645d0, [], SA_SIGINFO}, NULL, 8) = 0
  rt_sigprocmask(SIG_UNBLOCK, [RTMIN], NULL, 8) = 0
  getrlimit(RLIMIT_STACK, {rlim_cur=8192*1024, rlim_max=RLIM_INFINITY}) = 0
  --- SIGSEGV (Segmentation fault) @ 0 (0) ---
  +++ killed by SIGSEGV +++
 
 
 
  ¿Alguna sugerencia? Mil gracias.
 
 
 
  --
  Iñaki Baz Castillo
  [EMAIL PROTECTED]
 

 Si no ha habido actualización de por medio, el problema tiene que ser 
 hardware.

 Probaría a pasarle un memtest para ver la ram y/o probar con otro disco duro.

 A mi me pasó algo 

Re: Segmentation fault al hacer un ls en Sarge

[Iñaki Baz Castillo]

El 2/08/07, ChEnChO [EMAIL PROTECTED] escribió:

 Si no ha habido actualización de por medio, el problema tiene que ser 
 hardware.

No ha habido nada en principio.


 Probaría a pasarle un memtest para ver la ram y/o probar con otro disco duro.

Vale, lo único, he probado memtest all (que es como interpreto se
debe ejecutar el comando) y me ah colgado la máquina, ¿cómo debería
ejecutarlo?


 A mi me pasó algo similiar con un servidor y tras muchas pruebas, era
 un módulo de ram que había cascado.

Tomo nota, y agradezco tu ayuda ya que es una situación urgente que
tendré que ir ahora a revisar :X




-- 
Iñaki Baz Castillo
[EMAIL PROTECTED]

Re: Segmentation fault al hacer un ls en Sarge

[Iñaki Baz Castillo]

El 2/08/07, Adrià [EMAIL PROTECTED] escribió:
 Yo por mi parte te recomendaría mirar la integridad del disco duro, ya
 que esto fue lo que le pasó a uno de mis servidores.
 Por suerte, con un disco nuevo y los backups, en un día lo tuve funcionando :)

¿Por ejemplo un badblocks desde un live-cd?
Gracias.



-- 
Iñaki Baz Castillo
[EMAIL PROTECTED]

Re: Segmentation fault al hacer un ls en Sarge

[Emilio J. Padron]

On Thu, Aug 02, 2007 at 11:21:03AM +0200, Iñaki Baz Castillo wrote:
  Probaría a pasarle un memtest para ver la ram y/o probar con otro disco duro
 
 Vale, lo único, he probado memtest all (que es como interpreto se
 debe ejecutar el comando) y me ah colgado la máquina, ¿cómo debería
 ejecutarlo?

lo mejor sería que en este caso utilices un memtest que sea
independiente del SO (vamos, no el memtest que puedas tener en el
sistema que te está dando problemas). Tienes los paquetes memtest86 y
memtest86+ para ello, que te permiten arrancar el testeo desde grub o
lilo. 

Si el sistema está tan mal que no te permite siquiera instalar nuevos 
paquetes, tendrás que agenciarte un live-cd que lo incluya (hay
un montón por ahí).

Un saludo,
E.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: Segmentation fault al hacer un ls en Sarge

[Adrià]

On 8/2/07, Iñaki Baz Castillo [EMAIL PROTECTED] wrote:
 El 2/08/07, Adrià [EMAIL PROTECTED] escribió:
  Yo por mi parte te recomendaría mirar la integridad del disco duro, ya
  que esto fue lo que le pasó a uno de mis servidores.
  Por suerte, con un disco nuevo y los backups, en un día lo tuve funcionando 
  :)

 ¿Por ejemplo un badblocks desde un live-cd?
 Gracias.



 --
 Iñaki Baz Castillo
 [EMAIL PROTECTED]

Dependiendo de la urgencia (has dicho que el servidor está en
producción, no?) yo me plantearía ahora mismo ser resolutivos y
después caspar.
Depende de las posibilidades que tengas, quizás merecia la pena
obtener una nueva máquina (o hacer un frankenstein con piezas
antiguas) y sustituir -aunque sea de forma provisional- el servidor
afectado.

A partir de aquí, restaurar a partir de backups y, si puedes, con esta
receta [1].

Por lo que comentabas antes, si ejecutar memtest te ha colgado la
máquina, cambio mi apuesta de disco duro a RAM.

Saludos!

[1] 
http://mundogeek.net/archivos/2007/06/11/copia-de-seguridad-de-los-programas-instalados-en-linux/

-- 
Adrià García-Alzórriz
[EMAIL PROTECTED]

Re: Segmentation fault al hacer un ls en Sarge

[Iñaki Baz Castillo]

El 2/08/07, Adrià [EMAIL PROTECTED] escribió:
 Dependiendo de la urgencia (has dicho que el servidor está en
 producción, no?) yo me plantearía ahora mismo ser resolutivos y
 después caspar.
 Depende de las posibilidades que tengas, quizás merecia la pena
 obtener una nueva máquina (o hacer un frankenstein con piezas
 antiguas) y sustituir -aunque sea de forma provisional- el servidor
 afectado.

De hecho esa medida ya ha sido tomada y estamos en ello ;)


 Por lo que comentabas antes, si ejecutar memtest te ha colgado la
 máquina, cambio mi apuesta de disco duro a RAM.

Bueno, en realidad había colgado MI máquina al hacer un memtest all,
o igual es que tarda mucho mucho tiempo en el allocating
X
el caso es que en la máquina afectada se ha cambiado los zócalos de
RAM y el problema persiste, por lo que seuponemos será tema de disco y
estamos montando otra máquina.

Gracias por todo a todos los que me habéis ayudado.


-- 
Iñaki Baz Castillo
[EMAIL PROTECTED]

Re: segmentation fault in Mozilla browser

[L.V.Gandhi]

For me it didn't crash

On 12/20/05, H.S. [EMAIL PROTECTED] wrote:

 Hi,

 While reading the Slashdot news on the pirates bay, I noticed that when
 I click on this link:
 http://thepiratebay.org/legal.php

 it starts to load but before finishing Mozilla browser crashed. The
 message on the std out is segmentation fault. The above link is on
 this page:
 http://slashdot.org/comments.pl?sid=171669cid=14297749


 The webpage also crashes Firefox browser.

 I am using:
 ii  mozilla-browser   1.7.12-1
 ii  mozilla-firefox   1.0.7-1

 This is on Debian Testing, running 2.6.12-1-686 kernel.

 Anybody else having this problem?
 -HS


 --
 To UNSUBSCRIBE, email to [EMAIL PROTECTED]
 with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]




--
L.V.Gandhi
http://lvgandhi.tripod.com/
linux user No.205042

Re: segmentation fault in Mozilla browser

[steef]

H.S. wrote:


Hi,

While reading the Slashdot news on the pirates bay, I noticed that when
I click on this link:
http://thepiratebay.org/legal.php

it starts to load but before finishing Mozilla browser crashed. The
message on the std out is segmentation fault. The above link is on
this page:
http://slashdot.org/comments.pl?sid=171669cid=14297749


The webpage also crashes Firefox browser.

I am using:
ii  mozilla-browser   1.7.12-1
ii  mozilla-firefox   1.0.7-1

This is on Debian Testing, running 2.6.12-1-686 kernel.

Anybody else having this problem?
-HS


 

when i loaded - with the mozilla-plugin - the (newest, self-compiled) 
kaffeine to look at some news-pages in the browser (standard mozilla 
under sarge) seemingly without a system mozilla broke sometimes down 
with a *segmentation fault*


these crashes do *not* repeat with the *debian* kaffeine-plugin and the 
*debian* kaffeine package installed.


steef


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: Segmentation fault

[Marty]

[EMAIL PROTECTED] wrote:

I installed a copy of debian from the netinstall cd about 2 weeks ago. the
installation works fine but once I get the base system on and try to do
any apt-get commands every packet I try to download gives the error
segmentation fault and then goes back to prompt. I've tried many
different sources for the packets and every source I try to use ends up
with the same error.

Aaron Adamson




If possible, try different memory modules.  For some reason, dpkg seems
particularly sensitive to memory errors.

I once got repeated segfaults and perl warnings due to memory errors,
when almost no other test (including memtest) was able to detect the failures.



--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: Segmentation fault

[Roberto C. Sanchez]

On Tue, Aug 16, 2005 at 05:26:44PM -0400, Marty wrote:
 [EMAIL PROTECTED] wrote:
 I installed a copy of debian from the netinstall cd about 2 weeks ago. the
 installation works fine but once I get the base system on and try to do
 any apt-get commands every packet I try to download gives the error
 segmentation fault and then goes back to prompt. I've tried many
 different sources for the packets and every source I try to use ends up
 with the same error.
 Aaron Adamson
 
 If possible, try different memory modules.  For some reason, dpkg seems
 particularly sensitive to memory errors.
 
 I once got repeated segfaults and perl warnings due to memory errors,
 when almost no other test (including memtest) was able to detect the failures.
 
Although memtest did not work out for you, I have had ut successfully
detect faulty memory for me.  You may want to boot a Knoppix CD and run
memtest from it.

-Roberto

-- 
Roberto C. Sanchez
http://familiasanchez.net/~roberto


pgpTPdwDIYeyH.pgp
Description: PGP signature

Re: Segmentation fault

[[EMAIL PROTECTED]]

On 4/30/05, Ritesh Raj Sarraf [EMAIL PROTECTED] wrote:
 -BEGIN PGP SIGNED MESSAGE-
 Hash: SHA1
 
 [EMAIL PROTECTED] wrote:
 
  Anyway, I recommend you reinstall Sarge from scratch, using the
  netinst ISO image.  Since Sarge isn't released yet, doing an upgrade
  may not work well.
 
 If Sarge isn't released how will installing it from scratch help ?
 
 And Debian is known to be upgraded from releases to releases.

Sarge has not been finalized yet.  Therefore, there is a chance that
upgrading from Woody to Sarge may not work completely yet.  Since you
did upgrade from Woody to Sarge, it might not have gone completely
smoothly.  Installing clean from the Sarge installer may fix some of
the weird, hard-to-track-down problems you are having.  If you don't
want to try it, that's up to you.  :)

Re: Segmentation fault on startup

[David Baron]

On Tuesday 23 November 2004 23:03, [EMAIL PROTECTED] 
wrote:
  I am seeing the segmentation fault message as the startup scripts
  race by. Cannot retrieve it by dmesg afterwards. It is apparently
  (hopefully) harmless. Anybody else getting this. I have the most
  recent 2.6.8-4 kernel image off Sid.

 Activate the boot log daemon. Take a look at /etc/default/bootlogd. The
 log will be written to /var/log/boot.

BOOTLOGD_ENABLE=yes

is there. I am not gettling the boot log.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: segmentation fault in shib target: has anyone experienced this?

[Jon Dowland]

On Tue, 23 Nov 2004 10:21:59 -0500, Kanipe, Kent
[EMAIL PROTECTED] wrote:
 I had a bunch of problems like this and it was related to a combination
 of OS, and compiler version.  What setup are you built for?

Red Hat ES 3.0., kernel 2.4.21-15.EL
gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-34)
Apache/2.0.46 (as supplied)
OpenSSL 0.9.7a Feb 19 2003 (as supplied)

shibboleth-1.2.1
xml-security-c-1.1.0
xerces-c- 2.6.1
opensaml-1.0.1
log4cpp-0.3.4b
(all from wayf.internet2.edu/shibboleth/)

curl-7.11.1

Thanks,

-- 
Jon Dowland


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: segmentation fault in shib target: has anyone experienced this?

[Jon Dowland]

oops, apologies for the mis-reply. Got my lists mixed up.


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: Segmentation fault on startup

[Andreas Janssen]

Hello

David Baron ([EMAIL PROTECTED]) wrote:

 I am seeing the segmentation fault message as the startup scripts
 race by. Cannot retrieve it by dmesg afterwards. It is apparently
 (hopefully) harmless. Anybody else getting this. I have the most
 recent 2.6.8-4 kernel image off Sid.

Activate the boot log daemon. Take a look at /etc/default/bootlogd. The
log will be written to /var/log/boot.

best regards
 Andreas Janssen

-- 
Andreas Janssen [EMAIL PROTECTED]
PGP-Key-ID: 0xDC801674 ICQ #17079270
Registered Linux User #267976
http://www.andreas-janssen.de/debian-tipps-sarge.html


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: Segmentation fault (solved)

[Maurits van Rees]

On Mon, Oct 11, 2004 at 01:05:52AM -0400, Marek Pawinski wrote:
 [root:~]mkdir bak
 [root:~]mkdir bak/var 
 [root:~]mkdir bak/var/cache   
 [root:~]mkdir bak/var/cache/apt   
 [root:~]mkdir bak/var/cache/apt/bin

You should be able to do this in one command:

[root:~]mkdir -p bak/var/cache/apt/bin

The `-p' makes the bin directory and any Parent directories that do
not yet exist.

-- 
Maurits van Rees | [EMAIL PROTECTED] | http://maurits.vanrees.org/
Let your advance worrying become advance thinking and planning.
 - Winston Churchill


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: Segmentation fault

[ognen]

I have had this problem many times, and it was not  due to faulty 
hardware but rather a software issue with me (well it was partially 
hardware, it would corrupt the database creating the segmentation 
fault). There was a way of fixing it, i think you had to delete some 
files alas i cannot remember but a google search should yield more 
info (thats where i found out)

Jule Slootbeek wrote:
The last time i saw that error, it was because of a bad memory stick, 
download memtest86 (i assume you are running on a x86 machine) from 
www.memtest86.com and see if you have any corrupted memory.
hope this helps,
-JSS

Marek Pawinski wrote:
Hi
When i run apt-get install package i get a Reading Package 
Lists... Done
Segmentation faulty Tree... 50% error. I have tried apt-get check 
and apt-get clean, does not solve. Apt-get update seems to work. Any 
help please.

Marek



--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: Segmentation fault (solved)

[Marek Pawinski]

ognen wrote:
I have had this problem many times, and it was not  due to faulty 
hardware but rather a software issue with me (well it was partially 
hardware, it would corrupt the database creating the segmentation 
fault). There was a way of fixing it, i think you had to delete some 
files alas i cannot remember but a google search should yield more 
info (thats where i found out)

Jule Slootbeek wrote:
The last time i saw that error, it was because of a bad memory stick, 
download memtest86 (i assume you are running on a x86 machine) from 
www.memtest86.com and see if you have any corrupted memory.
hope this helps,
-JSS

Marek Pawinski wrote:
Hi
When i run apt-get install package i get a Reading Package 
Lists... Done
Segmentation faulty Tree... 50% error. I have tried apt-get check 
and apt-get clean, does not solve. Apt-get update seems to work. Any 
help please.

Marek



Thanks guys i found the solution here it is:
[root:~]mkdir bak
[root:~]mkdir bak/var 
[root:~]mkdir bak/var/cache   
[root:~]mkdir bak/var/cache/apt   
[root:~]mkdir bak/var/cache/apt/bin
[root:~]mv /var/cache/apt/*.bin ~/bak/var/cache/apt/bin


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: Segmentation fault - meaning

[Hans du Plooy]

On Thursday 08 January 2004 00:05, Leandro Guimares Faria Corcete Dutra 
wrote:
  I try to run it on the laptop I get a segmentation fault.  What does
  that mean, and what sorts of things might cause it?
 This is a but, plain and simple.  It means that the program tried to
 access some protected memory segment.

Worst case scenario, this could also mean your RAM is bad.  If you want to 
rule out this possibility, google for memtest - a bootable image that stress 
tests your RAM.

Hans


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: Segmentation fault - meaning

[James Tappin]

On Thu, 8 Jan 2004 09:30:33 +0200
Hans du Plooy [EMAIL PROTECTED] wrote:

 On Thursday 08 January 2004 00:05, Leandro Guimarães Faria Corcete Dutra 
 wrote:
   I try to run it on the laptop I get a segmentation fault.  What does
   that mean, and what sorts of things might cause it?
  This is a but, plain and simple.  It means that the program tried to
  access some protected memory segment.
 
 Worst case scenario, this could also mean your RAM is bad.  If you want to 
 rule out this possibility, google for memtest - a bootable image that stress 
 tests your RAM.

Or just apt-get install memtest86 and add it to /etc/lilo.conf


-- 
James Tappin, O__  I forget the punishment for using
[EMAIL PROTECTED]   --  \/`Microsoft --- Something lingering
http://www.tappin.me.uk/with data loss in it I fancy  


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: Segmentation fault - meaning

[Colin Watson]

On Wed, Jan 07, 2004 at 02:55:11PM +, Fred Richards wrote:
 I've installed a package on a PC, and then the same on a laptop.  When
 I try to run it on the laptop I get a segmentation fault.  What does
 that mean, and what sorts of things might cause it?

It's almost impossible to answer that usefully in such general terms.

A segmentation fault means that the program accessed an area of memory
which it was not supposed to access. It almost always indicates a bug:
for instance, a pointer to some memory might have been accidentally
overwritten with junk.

Beyond that, I'd need to see specifics.

Cheers,

-- 
Colin Watson  [EMAIL PROTECTED]


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: Segmentation fault - meaning

[Leandro Guimarães Faria Corcete Dutra]

Em Qua, 2004-01-07 s 12:55, Fred Richards escreveu:
 I've installed a package on a PC, and then the same on a laptop.  When
 I try to run it on the laptop I get a segmentation fault.  What does
 that mean, and what sorts of things might cause it?

This is a but, plain and simple.  It means that the program tried to
access some protected memory segment.

This is either an upstream bug, or a package version mismatch probably.


-- 
Leandro Guimares Faria Corcete Dutra [EMAIL PROTECTED]
Prefeitura do Municpio de So Paulo
Governo Eletrnico, Telecentros  +55 (11) 5080 9647
http://br.geocities.com./lgcdutra/   +55 (11) 5080 9648


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: segmentation fault

[Florian Zavatzki]

Hallo

Florian Wagner [EMAIL PROTECTED] wrote:

 XF86Conf:
 ...
 Section Module
 Load GLcore
 Load bitmap
 EndSection

Ich kann nicht genau sagen ob der segmentation fault etwas damit zu tun hat, aber die 
Module Section sollte anders aussehen.
Wenn du die Debian Packete fuer den Treiber verwendet hast, steht folgendes in 
/usr/share/doc/nvidia-glx/README.Debian (ansonsten in der README auf der NVidia Seite):
Minimum requirements:
In Section Module
   add Load glx
   remove Load dri
   remove Load GLcore

mfg
Florian


pgp0.pgp
Description: PGP signature

Re: segmentation fault

[jxz]

On Mon, Sep 29, 2003 at 04:03:15AM -0300, caio ferreira wrote:
: Qualquer coisa que eu venha fazer que exige algum ***processamento pesado***
: como a compilação de um kernel, aparece a mensagem Segmentation Fault

1) Sobreaquecimento do processador
2) Setores defeituosos no HD, que corromperam alguma biblioteca
importante.
3) Memoria defeituosa (as vezes voce precisa deixar varias horas para o
memtest encontrar algum erro).


-- 
[EMAIL PROTECTED]
http://jxz.dontexist.org/


pgpXQel6Y4529.pgp
Description: PGP signature

Re: segmentation fault no wget

[Douglas A. Augusto]

No dia 17/07/2003 às 15:34,
[EMAIL PROTECTED] escreveu:

 gente,
 O comando é este:
 ... 
 Tá foda. Já aconteceu três vezes hoje. Dei apt-get update; apt-get upgrade
 a mais ou menos uma semana atrás...
 
 Sugestões?

Já tive problemas de falha de segmentação com o wget. A propósito, você está
usando o wget da unstable?

-- 
Douglas Augusto

Re: segmentation fault no wget

[fredm]

 No dia 17/07/2003 às 15:34,
 [EMAIL PROTECTED] escreveu:

  gente,
  O comando é este:
  ...
  Tá foda. Já aconteceu três vezes hoje. Dei apt-get update; apt-get
upgrade
  a mais ou menos uma semana atrás...
 
  Sugestões?

 Já tive problemas de falha de segmentação com o wget. A propósito, você
está
 usando o wget da unstable?

Não. Meu sistema é totalmente woody. E outra coisa. Rodei de novo com a
opção -b, como falei que ia fazer e não deu pau nenhum. Fiquei olhando com
tail -f -n 20 wget-log. Agora, eu não sei se foi coincidência ou não.
Semana que vem, quando eu fizer o processo de novo, vou tentar com -b desde
o começo para ver o que acontece.

Re: segmentation fault

[Leandro Guimarães Faria Corsetti Dutra]

Em Wed, 09 Jul 2003 16:37:33 -0300, fred escreveu:

 Tue, Jul 08, 2003 at 04:30:00PM -0300, [EMAIL PROTECTED]:
 
 Segfault é uma falha de segmentação que pode ocorrer com qualquer
 programa. Isso acontece se o programa que você está usando tem um bug,
 
 foi o wget, baixando as atulaizações de segurança do potato, do slink, do
 sarge
 e do woody... E quanto aos logs? Era para ele deixar um core-sei-lá-o-que
 em
 algum lugar?

Não, quando há segfault é pau mesmo, nada de log.  Eu sugeriria 
verificar
se não há um relato de erro do wget, se possível atualizá-lo...


-- 
 _
/ \  Leandro Guimarães Faria Corsetti Dutra +41 (21) 648 11 34
\ /  http://br.geocities.com./lgcdutra/ +41 (78) 778 11 34
/ \  Responda à lista, não a mim diretamente!   +55 (11) 5686 2219
Dê-me nota se te ajudei:   http://svcs.affero.net/rm.php?r=leandro

Re: segmentation fault

[José de Paula]

Em Wed, Jul 09, 2003 at 04:37:33PM -0300, [EMAIL PROTECTED] escreveu:
 
 
 
 
  Tue, Jul 08, 2003 at 04:30:00PM -0300, [EMAIL PROTECTED]:
   Povo,
 
  Olá Magalhães :),
 
 
 Eu mereço...
 
   Por que acontece o segmentation fault? Eu estava tranquilamente
 baixando
   um espelho das atualizações de segurança do debian quando aconteceu a
   primeira vez. Rodei de novo, e uns minutos depois aconteceu de novo.
 Que
   howto trata do assunto? Ele deixa rastro em algum log? Olhei no
 /var/log e
   não achei nenhum nome muito sugestivo.
 
  Segfault é uma falha de segmentação que pode ocorrer com qualquer
  programa. Isso acontece se o programa que você está usando tem um bug,
  e/ou foi mal programado. Quando um programa precisa ler parte da memória
  que não foi devidamente inisializada, ou não pertence ao programa,
  acontece isso e o kernel geralmente termina o programa. Primeiro temos
  então que sager qual programa você está usando.
 
 foi o wget, baixando as atulaizações de segurança do potato, do slink, do
 sarge
 e do woody... E quanto aos logs? Era para ele deixar um core-sei-lá-o-que
 em
 algum lugar?
 
Core dump; um arquivinho chamado core deixado no seu $HOME. É útil para
desenvolvedores depurarem o programa, acharem o que é que está errado.

Quando eu tinha um AMD-K6 e o cooler passou a ter problemas
(processador AMD + cooler defeituoso = superaquecimento da CPU), eu
tinha vários segmentation faults, mesmo em programas considerado
estáveis, como o mutt e procmail, além de reinicializações sem mais nem
menos. Troquei o cooler, acabou-se o problema. Só para constar.

 

Re: segmentation fault

[Claudio Clemens]

Tue, Jul 08, 2003 at 04:30:00PM -0300, [EMAIL PROTECTED]:
 Povo,

Olá Magalhães :),

 Por que acontece o segmentation fault? Eu estava tranquilamente baixando
 um espelho das atualizações de segurança do debian quando aconteceu a
 primeira vez. Rodei de novo, e uns minutos depois aconteceu de novo. Que
 howto trata do assunto? Ele deixa rastro em algum log? Olhei no /var/log e
 não achei nenhum nome muito sugestivo.

Segfault é uma falha de segmentação que pode ocorrer com qualquer
programa. Isso acontece se o programa que você está usando tem um bug,
e/ou foi mal programado. Quando um programa precisa ler parte da memória
que não foi devidamente inisializada, ou não pertence ao programa,
acontece isso e o kernel geralmente termina o programa. Primeiro temos
então que sager qual programa você está usando.

Até

Claudio

-- 
+- .''`. ---| Claudio Clemens in Germany now |--| Sid |---+
| : :' :   asturio at gmx.netGNU/Linux User #79942|
| `. `'To C or not to C? That's the question!   |
|   `- YE GODS, I HAVE FEET??! - Userfriendly  |
Scotty! Hurry! Beam me uragg^*·)(@$þ£ NO CARRIER


pgp8fOFCu770j.pgp
Description: PGP signature

Re: segmentation fault

[fredm]

 Tue, Jul 08, 2003 at 04:30:00PM -0300, [EMAIL PROTECTED]:
  Povo,

 Olá Magalhães :),


Eu mereço...

  Por que acontece o segmentation fault? Eu estava tranquilamente
baixando
  um espelho das atualizações de segurança do debian quando aconteceu a
  primeira vez. Rodei de novo, e uns minutos depois aconteceu de novo.
Que
  howto trata do assunto? Ele deixa rastro em algum log? Olhei no
/var/log e
  não achei nenhum nome muito sugestivo.

 Segfault é uma falha de segmentação que pode ocorrer com qualquer
 programa. Isso acontece se o programa que você está usando tem um bug,
 e/ou foi mal programado. Quando um programa precisa ler parte da memória
 que não foi devidamente inisializada, ou não pertence ao programa,
 acontece isso e o kernel geralmente termina o programa. Primeiro temos
 então que sager qual programa você está usando.

foi o wget, baixando as atulaizações de segurança do potato, do slink, do
sarge
e do woody... E quanto aos logs? Era para ele deixar um core-sei-lá-o-que
em
algum lugar?

Re: segmentation fault

[Dr. Aldo Medina]

German Garcia wrote:
 
 On Thu, Dec 19, 2002 at 08:42:40AM -0700, [EMAIL PROTECTED] wrote:
  por que puede ser que cuando hago un
  ps, top
  me larga una violación de segmento a que se puede deber esto
 -Que version de Debian tenes instalada ?
 -Solo te pasa con estos programas o tambien con otros ?
 -Estas usando un kernel compilado por vos ?
 -Tenes la pc overclockeada ?
 
 --
 German Garcia   | Debian GNU/Linux
 [EMAIL PROTECTED]  | vi - c - c++
 Buenos Aires, Argentina | Barrio de Tango

Otra posibilidad es que te hayan crackeado la máquina y el ps, el top o
ambos hayan sido modificados para no mostrar el regalito, pero
tenga(n) errores en la programación. Soy algo paranoico :-D

-- 
Linux User #98419 -o)| Pon a volar tu mente... ¡¡Fuma
http://counter.li.org  /\| dinamita!!  
ICQ 94335020  _\_v   | 
 | 
 |

Re: segmentation fault

[German Garcia]

On Thu, Dec 19, 2002 at 08:42:40AM -0700, [EMAIL PROTECTED] wrote:
 por que puede ser que cuando hago un
 ps, top
 me larga una violación de segmento a que se puede deber esto 
-Que version de Debian tenes instalada ?
-Solo te pasa con estos programas o tambien con otros ?
-Estas usando un kernel compilado por vos ?
-Tenes la pc overclockeada ?

-- 
German Garcia   | Debian GNU/Linux 
[EMAIL PROTECTED]  | vi - c - c++ 
Buenos Aires, Argentina | Barrio de Tango

Re: segmentation fault - XEphem

[Wayne Topa]

Glenn Becker([EMAIL PROTECTED]) is reported to have said:
 Hi -
 
 I can't pinpoint *exactly* when this problem began. I'm running testing
 (sarge) with a few unstable packages thrown in. 
 
 Anyway, I installed the commercial/CD package of the XEphem astronomy
 program some months ago and have been happily running it since. Last
 week, however, I started getting a segmentation fault when I tried to
 run the program.


I am running xephem 3.5-2, from testing (I think), and it runs fine.
Suggest you use the CD for the Win version and just get the deb
package.  I seem to recall that a while ago I had used xephem-smotif,
so I check the dependices for xephem and see

VT1 root-3-Buddy:~# deps xephem
xephem
  Depends: lesstif1
  Depends: libc6
  Depends: xlibs
  Conflicts: xephem-smotif
  Conflicts: xephem-dmotif
  Replaces: xephem-smotif
  Replaces: xephem-dmotif

That might be the problem(?)

HTH
-- 
Windows: the ultimate triumph of marketing over technology.
___


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: segmentation fault - XEphem

[Glenn Becker]

Wayne -

 I am running xephem 3.5-2, from testing (I think), and it runs fine.
 Suggest you use the CD for the Win version and just get the deb
 package.  

This was a good suggestion, though I have the UNIX CD. :) CD version
still works fine on my old laptop, which runs Slackware 8.1.

What I did was uninstall, install the XEphem .deb, then copy the data
files over from the CD. Works great now.

Thx,

Glenn


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Re: segmentation fault

[Marcin Owsiany]

On Sun, Nov 03, 2002 at 05:19:43PM +0100, Bartosz Dabrowski wrote:
 Sorry za moja niewiedze, ale ostatnio sobie cos pisalem w cpp i caly czas
 przy odpalaniu programikow wyskakuje mi segmentation fault podczas gdy w
 windzie te programy uruchamiaja sie  poprawnie. Na czym polega segmentation
 fault 

Naruszenie segmentacji oznacza, że proces próbował odwołać się do
obszaru pamięci, który nie został mu przydzielony. Pod windows nazywa
się to chyba segmentation violation.
Jak łatwo się domyśleć nie każde błędne odwołanie powoduje naruszenie
segmentacji - zależy to od wielkości i umiejscowienia konkretnych
segmentów no i charakteru samego błędu...

 i co trzeba zrobic zeby przestal wyskakiwac?

Poprawić program :-)
Masz do dyspozycji:
* -Wall
* electric-fence (nie wiem czy działa pod c++, ale jeśli nie to pewnie
  znajdziesz coś podobnego)
* gdb

Marcin
-- 
Marcin Owsiany [EMAIL PROTECTED] http://marcin.owsiany.pl/
GnuPG: 1024D/60F41216  FE67 DA2D 0ACA FC5E 3F75  D6F6 3A0D 8AA0 60F4 1216

Re: segmentation fault

[Tobias Jahn]

Hi toto!

On Mon, Jun 10, 2002 at 11:13:07AM +0200, toto wrote:
 wenn ich bei der ausführung eines programmes ein 'segmentation fault'
 zurück kriege , was ist dann?

ask google ;-)

Z.B.: http://www.tuxedo.org/~esr/jargon/html/entry/segmentation-fault.html

Bekommst du das bei einem eigen Programm oder einem fertigen Paket?

-- 
Greetings,
Tobias


PGP/GnuPG Key ID 0xAE034AAD (preferred)



msg10102/pgp0.pgp
Description: PGP signature

Re: segmentation fault

[Tobias Jahn]

On Mon, Jun 10, 2002 at 11:59:56AM +0200, Torsten Puls wrote:
 Z.B.: http://www.tuxedo.org/~esr/jargon/html/entry/segmentation-fault.html
 
 Bekommst du das bei einem eigen Programm oder einem fertigen Paket?

 das weiß ich jetzt nicht mehr. ich will nur das grundlegende verstehen.

Dieses Signal wird erzeugt, wenn ein Prozess auf einen Speicherbereich
zugreift, der ihm nicht gehoert (den er also z.B. nicht mit malloc reserviert
hat).

 was ist bei einem eigenem programm und was bei einem fertigen paket?

Bei einem eigenen Programm ist das meist ein Tippfehler, in einem fertigen
Programm oft ein Bug, der in Faellen auftritt, die der Entwickler (noch) nicht
testen konnte ;-)

Kurz  gut: Konkreter laesst sich das nicht sagen, da die Ursachen vielfaeltig
sind ;-)

Btw, auf win32-System lautet das ganze so aehnlich wie allgemeine
Schutzverletzung ;-)

-- 
Greetings,
Tobias


PGP/GnuPG Key ID 0xAE034AAD (preferred)


-- 
Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED]
mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)

Re: Segmentation fault, ese incordio

[Fernando Taboada]

Probablemente se trata de un problema hardware de algún tipo.
Existe un FAQ para la señal 11 (Violación de segmento) en algún
lugar de Internet que no recuerdo (y no tengo Internet a mano :-(
Busca en Google como Sig11 FAQ o por Segmentation Fault FAQ
o algo así... aparece seguro!

A mi me pasa desde que instalé un nuevo módulo de memoria...
y a lo mejor dañe alguna pista en la placa o algún banco de memoria
y ahora me pasa con frecuencia aunque no me impide trabajar de momento.

Suerte!


[EMAIL PROTECTED] wrote:

 From: [EMAIL PROTECTED]
 To: debian-user-spanish@lists.debian.org
 Date: Mon, 25 Feb 2002 09:37:06 +0100
 Subject: Segmentation fault, ese incordio
 Message-Id: [EMAIL PROTECTED]

 ==
 Juan Manuel Enrique Muñido
 ==
 E-mail: [EMAIL PROTECTED]
 Teléfono: 676853151
 ==

   
Name: TXT0.TXT
TXT0.TXTType: Plain Text (text/plain)
Encoding: base64

Re: Segmentation fault, ese incordio

[Juan \(Casa\)]

Fernando Taboada wrote:
 
 Probablemente se trata de un problema hardware de algún tipo.
 Existe un FAQ para la señal 11 (Violación de segmento) en algún
 lugar de Internet que no recuerdo (y no tengo Internet a mano :-(
 Busca en Google como Sig11 FAQ o por Segmentation Fault FAQ
 o algo así... aparece seguro!

Buenas. Yo tengo este enlace, http://www.BitWizard.nl/sig11/, por si
sirve de algo.
Un saludo.
-- 
Web imprescindible para todo principiante de Linux
http://www.escomposlinux.org
Por una Tarifa Plana Universal y Asequible (RTB)
http://mienten.com

Re: segmentation fault with kmail and attachements: what am I doing wrong?

[Hans Ekbrand]

On Fri, Jan 04, 2002 at 10:38:52AM +0100, rdiaz wrote:
 Dear All,
 
 A few days ago I installed Woody (after a couple of years of suse). 
 Everything seems fine, but I am having a problem with Kmail (4:2.1.1-7). 
  It crashes as soon as I try to include an attachement (segmentation 
 fault, signal 11) in a new message.


Same problem here.


 I think I must be doing something stupid, since I have searched in this 
 list and the bug reports, and I cannot find anything similar. I have 
 tried a whole bunch of possible combinations: installing the full set of 
 kde packages (kdebase, konqueror, etc), installing only the required 
 libraries for kmail (kdelibs3 and kdebase-libs), purging and 
 reinstalling, etc, etc. Package installation (either from dselect or 
 directly using dpkg -i) aparently proceeds without problems, but still I 
 always get the segmentation fault when trying to include the 
 attachement, regardless of size and type of attachement.
 
 Can anybody suggest what I might try?

Sorry, but I can confirm the buggy behaviour of kmail. kmail -v gives:

Qt: 2.3.1
KDE: 2.2.2
KMail: 1.2

I have had testing and unstable in sources.list for apt, so it might
be a unusual combination of versions.


pgpqmMVtIDt31.pgp
Description: PGP signature

Re: Segmentation Fault w/ XF86Setup

[Jerome Acks Jr]

Rafe B. wrote:



I just tried to upgrade my potato box with 
XFree86 from unstable.  Bad idea?



Not the best.




This yields Segmentation Fault when I run XF86Setup.

So my questions are:

1. Was it dumb to install XF86 4.1 on 
top of a 2.2r3 base (kernel 2.2.18pre21) ?



Yes, if you mean installing XFree86 4.1 from unstable.
No, if you used unofficial XFree86 4.1 packages for potato.

Look at:
http://lists.debian.org/debian-x/2001/debian-x-200109/msg00042.html




2. Is it possible that XF86Setup itself was 
somehow not updated?




3. Which deb contains XF86Setup?  Danged 
if I can figure it out...



xf86setup
It is only found in potato. To configure XFree86 4.1, use
dpkg-reconfigure xserver-xfree86
or
XFree86 -configure




4. What's the minimim base for running 
XF86 version 4.1.0-9?  Or is apt-get 
supposed to deal with such dependencies?




Use apt-get or dselect to deal with dependencies.
But there will probably so many upgraded packages to solve dependencies, 
you might as well install sid.





5. Suggestions on where to go from here...




If I were you, I would consider either:
1. Reinstall potato packages you upgraded, and then install unofficial 
XFree86 4.1 packages for potato.


or

2. Do a distribution upgrade to woody or sid. (There have been a number 
of messages in this list discussing the best way to do this.)



I hope this helps.

--
Jerome

Re: Segmentation Fault w/ XF86Setup

[Frank Zimmermann]

I just tried to upgrade my potato box with
XFree86 from unstable.  Bad idea?


Yes!



This yields Segmentation Fault when I run XF86Setup.

Mildly chaotic update process, since I was
a bit confused about the Deb packages to get.
I started with:

  xfree86-common
  x-window-system-core
  xserver-common

.. at which point XF86Setup still ran, but
showed no video boards to select from.  Then
I went and got:

  xserver-svga


That is version 3.3.6-39


  xserver-xfree86
  libgnomesupport0
  libgnomeui32
  libgnome-perl  // and finally:
  x-window-system


version 4.1.x



.. which is probably where I should have
started.


You have a mixture of 3.3.6 and 4.1 packages on your system



So my questions are:

1. Was it dumb to install XF86 4.1 on
top of a 2.2r3 base (kernel 2.2.18pre21) ?


No but the wrong way of doing. Looks like you didn't even have a look 
on the packeges numbers.




2. Is it possible that XF86Setup itself was
somehow not updated?


XF86Setup is for 3.3.x



4. What's the minimim base for running
XF86 version 4.1.0-9?  Or is apt-get
supposed to deal with such dependencies?


apt-get is your choice. Go to http://people.debian.org/~bunk/ and 
read the instructions on how to install XF4 on potato with apt-get.




5. Suggestions on where to go from here...


Whew!  Many thanks in advance.  I'm way over
my head here, I guess g.


rafe b.


Frank
--

Re: Segmentation fault

[Colin Watson]

On Mon, Oct 29, 2001 at 11:54:17PM +0100, Raffaele Sandrini wrote:
 adding /usr/man to manpath
 /usr/share/man is already in the manpath
 /usr/X11R6/man is already in the manpath
 /usr/local/man is already in the manpath
 -

[segfault]

Hmm. The next thing man normally does after that is related to the
current locale. Could you tell me what this outputs?

  echo LC_ALL=$LC_ALL
  echo LC_MESSAGES=$LC_MESSAGES
  echo LANG=$LANG
  echo LANGUAGE=$LANGUAGE

I suspect add_nls_manpath() is buggy.

Thanks,

-- 
Colin Watson  [EMAIL PROTECTED]

Re: Segmentation fault

[Raffaele Sandrini]

 Hi Raffaele,

 If you tell me the version number of the man-db package you have
 installed, I'll try to debug this.

 Thanks,

I have version 2.3.20-6 of man-db installed.

cheers,
Raffaele
-- 
Raffaele Sandrini [EMAIL PROTECTED]
For encrypted Mail get my Public Key from search.keyserver.net
ID: 0xEC4950E9

Re: Segmentation fault

[Karsten M. Self]

on Mon, Oct 29, 2001 at 03:36:17PM +0100, Raffaele Sandrini ([EMAIL PROTECTED]) 
wrote:
 Hi,
 
 I can't use man anymore. On every manpage i get a segmentation fault. 
 Im using the 2.4.13-ac4 kernel.
 any hints?

$ strace man foo

Post the last hundred or so lines of output.  *Not* the whole damned 
thing.

Peace.

-- 
Karsten M. Self kmself@ix.netcom.com   http://kmself.home.netcom.com/
 What part of Gestalt don't you understand? Home of the brave
  http://gestalt-system.sourceforge.net/   Land of the free
   Free Dmitry! Boycott Adobe! Repeal the DMCA! http://www.freesklyarov.org
Geek for Hire http://kmself.home.netcom.com/resume.html


pgpQIDC8zBouk.pgp
Description: PGP signature

Re: Segmentation fault

[Colin Watson]

On Mon, Oct 29, 2001 at 03:36:17PM +0100, Raffaele Sandrini wrote:
 Hi,
 
 I can't use man anymore. On every manpage i get a segmentation fault. 

What version of man-db? Post the end of an strace (as Karsten said) as
well as the output of 'man -d somemanpage'.

-- 
Colin Watson  [EMAIL PROTECTED]

Re: Segmentation fault

[Raffaele Sandrini]

On Monday 29 October 2001 20:38, Karsten M. Self wrote:
 on Mon, Oct 29, 2001 at 03:36:17PM +0100, Raffaele Sandrini ([EMAIL 
 PROTECTED]) 
wrote:
  Hi,
 
  I can't use man anymore. On every manpage i get a segmentation fault.
  Im using the 2.4.13-ac4 kernel.
  any hints?

 $ strace man foo
Hi again,

here the output of strace man ls
-
open(/lib/libc.so.6, O_RDONLY)= 3
read(3, \177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0\270\327..., 1024) = 
1024
fstat64(0x3, 0xbfffedbc)= 0
old_mmap(NULL, 1187712, PROT_READ|PROT_EXEC, MAP_PRIVATE, 3, 0) = 0x4001a000
mprotect(0x40132000, 40832, PROT_NONE)  = 0
old_mmap(0x40132000, 24576, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED, 3, 
0x117000) = 0x40132000
old_mmap(0x40138000, 16256, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x40138000
close(3)= 0
open(/usr/local/qt3/lib/libdb2.so.2, O_RDONLY) = -1 ENOENT (No such file or 
directory)
open(/usr/local/lib/libdb2.so.2, O_RDONLY) = -1 ENOENT (No such file or 
directory)
open(/opt/kde/lib/libdb2.so.2, O_RDONLY) = -1 ENOENT (No such file or 
directory)
open(i686/mmx/libdb2.so.2, O_RDONLY)  = -1 ENOENT (No such file or 
directory)
open(i686/libdb2.so.2, O_RDONLY)  = -1 ENOENT (No such file or 
directory)
open(mmx/libdb2.so.2, O_RDONLY)   = -1 ENOENT (No such file or 
directory)
open(libdb2.so.2, O_RDONLY)   = -1 ENOENT (No such file or 
directory)
open(/lib/libdb2.so.2, O_RDONLY)  = 3
read(3, \177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0\0_\0\000..., 1024) = 
1024
fstat64(0x3, 0xbfffedac)= 0
old_mmap(NULL, 265836, PROT_READ|PROT_EXEC, MAP_PRIVATE, 3, 0) = 0x4013c000
mprotect(0x4017c000, 3692, PROT_NONE)   = 0
old_mmap(0x4017c000, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED, 3, 
0x3f000) = 0x4017c000
close(3)= 0
munmap(0x40016000, 14566)   = 0
umask(022)  = 022
brk(0)  = 0x80635d4
brk(0x80635fc)  = 0x80635fc
brk(0x8064000)  = 0x8064000
fstat64(0, 0xb89c)  = 0
fstat64(0x1, 0xb89c)= 0
fstat64(0x2, 0xb89c)= 0
getcwd(/root, 4094)   = 6
SYS_199(0x40137058, 0, 0x40137d60, 0x40134e70, 0xb97c) = 6
semop(1075015768, 0x40134e70, 0)= 6
ioctl(0, TCGETS, {B38400 opost isig icanon echo ...}) = 0
ioctl(1, TCGETS, {B38400 opost isig icanon echo ...}) = 0
ioctl(0, TIOCGWINSZ, {ws_row=30, ws_col=80, ws_xpixel=0, ws_ypixel=0}) = 0
open(/root/.manpath, O_RDONLY)= -1 ENOENT (No such file or 
directory)
open(/etc/manpath.config, O_RDONLY)   = 3
fstat64(0x3, 0xbfffd49c)= 0
old_mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 
0x40016000
read(3, # manpath.config\n#\n# This file i..., 4096) = 4096
read(3, n the order listed here;\n# the d..., 4096) = 570
read(3, , 4096)   = 0
close(3)= 0
munmap(0x40016000, 4096)= 0
ioctl(1, TCGETS, {B38400 opost isig icanon echo ...}) = 0
ioctl(0, TCGETS, {B38400 opost isig icanon echo ...}) = 0
rt_sigaction(SIGINT, {0x804e330, [INT], SA_RESTART|0x400}, {SIG_DFL}, 8) = 
0
stat64(0x8063a08, 0xb724)   = 0
stat64(0x8063a50, 0xb724)   = -1 ENOENT (No such file or 
directory)
stat64(0x80639b8, 0xb724)   = -1 ENOENT (No such file or 
directory)
stat64(0x8063928, 0xb724)   = 0
stat64(0x8063ae8, 0xb724)   = 0
stat64(0x8063ef0, 0xb714)   = 0
stat64(0x8063ef0, 0xb724)   = 0
stat64(0x8063ef0, 0xb714)   = -1 ENOENT (No such file or 
directory)
stat64(0x8063f30, 0xb714)   = -1 ENOENT (No such file or 
directory)
stat64(0x8063ef0, 0xb714)   = 0
stat64(0x8063ef0, 0xb724)   = 0
stat64(0x8063ef0, 0xb714)   = -1 ENOENT (No such file or 
directory)
stat64(0x8063ef0, 0xb714)   = -1 ENOENT (No such file or 
directory)
stat64(0x80639b8, 0xb724)   = -1 ENOENT (No such file or 
directory)
stat64(0x80637a0, 0xb724)   = 0
brk(0x8065000)  = 0x8065000
brk(0x8066000)  = 0x8066000
--- SIGSEGV (Segmentation fault) ---
+++ killed by SIGSEGV +++


and here the output of man -d ls
--
ruid=6, euid=6
++priv_drop_count = 1
From the config file /etc/manpath.config:

Mandatory mandir `/usr/man'.
Mandatory mandir `/usr/share/man'.
Mandatory mandir `/usr/X11R6/man'.
Mandatory mandir `/usr/local/man'.
Path `/bin' mapped to mandir `/usr/share/man'.
Path `/usr/bin' mapped to mandir `/usr/share/man'.
Path `/sbin' mapped to mandir `/usr/share/man'.
Path `/usr/sbin' mapped to mandir `/usr/share/man'.
Path `/usr/local/bin' mapped to mandir `/usr/local/man'.
Path 

Re: Segmentation fault

[Colin Watson]

On Mon, Oct 29, 2001 at 11:54:17PM +0100, Raffaele Sandrini wrote:
 On Monday 29 October 2001 20:38, Karsten M. Self wrote:
  $ strace man foo
 
 Hi again,
 
 here the output of strace man ls
[...]
 and here the output of man -d ls

Hi Raffaele,

If you tell me the version number of the man-db package you have
installed, I'll try to debug this.

Thanks,

-- 
Colin Watson  [EMAIL PROTECTED]

Re: segmentation fault??

[BURLET Frederic]

 Hi,

 This is my first time to meet this message and don't know why.
 The story is.
 This afternoon, I tried to install ssh3 for higher security.
 Follow standard step:
 configure
 make
 make install

 everything was fine, no error message showed on the screen.
 But, I can not connect to my server by ssh client server from poor win98.
 (This is another problem _)

For this problem (someone corrects me if I'm saying stupid things), you
have to configure ssh with --with-apm option thus: ./configure --with-apm

 So, I read FAQ. In FAQ said that I must check my ssh version,
 use command ssh -V . I did it, and then showed segmentation fault on my
 screen..
 Why???

Er... for this one... sorry :-( no idea

Fred.

 It is just simple command.
 Hope someone can tell me why. Please!! *_*
 And thanks for who read this mail.^^

 haheho

Re: Segmentation fault

[Stephane Monlibert - Sun france - ES - Support Engineer]

 Bonjour
 J'ai installé un debian noyau linux 2.4.9 comme passerelle internet avec
 iptables. La connexion est assurée par une carte isdn.
 Le tout tourne avec un pentium 166 MHZ et 24Mo de memoire
 Quand je tape :
isdnctrl status ippp0
 j'ai :
ippp0 connected to 0860888080
Segmentation fault
 
 C'est sûrement pas bon. Que dois-je envisager pour de plus avoir cette
 erreur.
 Merci

Segmentation fault est malheureusement un message tres generique
generalement un core est genere et pour savoir precisement d'ou vient le 
probleme il faut analyser le core avec sdb, mais malheureusement ceci n'est pas 
si simple.

Re: Segmentation fault

[Stephane Leclerc]

Tu peux aussi lancer la commande isdnctrl avec strace, voir man strace et
envoyer le résultat au mainteneur.

Stef...


 Quand je tape :
isdnctrl status ippp0
 j'ai :
ippp0 connected to 0860888080
Segmentation fault
 
 C'est sûrement pas bon. Que dois-je envisager pour de plus avoir cette
 erreur.
 Merci
 
 Segmentation fault est malheureusement un message tres generique
 generalement un core est genere et pour savoir precisement d'ou vient le
 probleme il faut analyser le core avec sdb, mais malheureusement ceci n'est
 pas 
 si simple.


..
.  Linux - Debian - php4 - Apache - MySQL - Infogerance  .
.   email: [EMAIL PROTECTED] - http://www.actionweb.fr   .
. Tel: (0)141 906 100-Fax: (0)141 906 101.
..

Re: Segmentation Fault All possible solutions Please.

[Oliver Elphick]

[EMAIL PROTECTED] wrote:
  Dear members,
 Here is something I have not been really been able to understand .. SEGME
  NTATION
  FAULT .
   Please tell m:
  1)What exactly is segmentation fault ?
  2)When does it occur ?
  3)How Do you Solve it ?
 
It means that a program has tried to address memory that does not belong
to it.

It is likely to occur if the program uses an uninitialised pointer.  There
can be many causes, all of which come down to programmer error.

You solve it first by using the debugger to find the pointer which is
at fault and second by carefully writing your programs so that they
never try to access invalid pointers.

-- 
Oliver Elphick[EMAIL PROTECTED]
Isle of Wight  http://www.lfix.co.uk/oliver
PGP: 1024R/32B8FAA1: 97 EA 1D 47 72 3F 28 47  6B 7E 39 CC 56 E4 C1 47
GPG: 1024D/3E1D0C1C: CA12 09E0 E8D5 8870 5839  932A 614D 4C34 3E1D 0C1C
 
 For whosoever shall call upon the name of the Lord 
  shall be saved. Romans 10:13