Hello! > > Could you please describe what you did to get the problem to occur? > It seems like you are running strace on lnstat and get a segmentation > fault.
The problem occurs in the shell (zsh and bash): % lnstat zsh: segmentation fault lnstat % bash [EMAIL PROTECTED]:~/tmp# lnstat Speicherzugriffsfehler Speicherzugriffsfehler means segmentation fault :-(. > Running lnstat here works without problems. Fine! > The strace doesn't > help locate the problem, a proper backtrace from gdb is needed. Which commands in which order are required? > If you could provide some more information about your environment > (kernel version, Linux 2.6.22-2-686 #1 SMP Fri Aug 31 00:24:01 UTC 2007 i686 GNU/Linux > contents of files opened by lnstat - > like /proc/net/stat/arp_cache see below > and other opened files, at the time you're running it lnstat opens successfully following files: /proc/net/stat/ip_conntrack entries searched found new invalid ignore delete delete_list insert insert_failed drop early_drop icmp_error expect_new expect_create expect_delete 00000001 000000cb 00049d1e 00000dae 000000eb 00000263 00000dad 000009cb 000009cc 00000000 00000000 00000000 00000047 00000000 00000000 00000000 /proc/net/stat/nf_conntrack entries searched found new invalid ignore delete delete_list insert insert_failed drop early_drop icmp_error expect_new expect_create expect_delete 00000001 000000cb 00049d1e 00000dae 000000eb 00000263 00000dad 000009cb 000009cc 00000000 00000000 00000000 00000047 00000000 00000000 00000000 /proc/net/stat/ndisc_cache entries allocs destroys hash_grows lookups hits res_failed rcv_probes_mcast rcv_probes_ucast periodic_gc_runs forced_gc_runs 00000001 00000007 00000006 00000001 00000010 00000009 00000000 00000000 00000000 00002f5a 00000000 /proc/net/stat/clip_arp_cache entries allocs destroys hash_grows lookups hits res_failed rcv_probes_mcast rcv_probes_ucast periodic_gc_runs forced_gc_runs 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 000023d1 00000000 /proc/net/stat/rt_cache entries in_hit in_slow_tot in_slow_mc in_no_route in_brd in_martian_dst in_martian_src out_hit out_slow_tot out_slow_mc gc_total gc_ignored gc_goal_miss gc_dst_overflow in_hlist_search out_hlist_search 00000004 0002cabb 00000296 00000000 00000000 00000036 00000021 00000000 0000201d 00000545 00000000 00000000 00000000 00000000 00000000 00000096 00000023 /proc/net/stat/arp_cache entries allocs destroys hash_grows lookups hits res_failed rcv_probes_mcast rcv_probes_ucast periodic_gc_runs forced_gc_runs 00000001 0000000e 0000000d 00000000 00000626 00000574 00000029 00000000 00000000 000023d1 00000000 > and other relevant information) that would be very helpful in > trying to reproduce and/or locate the problem. Which further information could be relevant? Thanks, Markus -- GMX FreeMail: 1 GB Postfach, 5 E-Mail-Adressen, 10 Free SMS. Alle Infos und kostenlose Anmeldung: http://www.gmx.net/de/go/freemail -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
