Mailinglist Archive: opensuse-bugs (6105 mails)

[bugzilla_noreply@xxxxxxxxxx]

https://bugzilla.novell.com/show_bug.cgi?id=258433#c23





--- Comment #23 from Kern Sibbald <kern@xxxxxxxxxxx>  2007-07-05 16:07:43 MST ---
I don't know what you need to reproduce it.  I am running:
Linux rufus 2.6.18.8-0.3-bigsmp #1 SMP Tue Apr 17 08:42:35 UTC 2007 i686 i686
i386 GNU/Linux
which as far as I am aware is a perfectly stock released SuSE 10.2.  I run my
program under the debugger and send it a signal 11, and I get:


Program received signal SIGSEGV, Segmentation fault.
0xb7f46410 in ?? ()
(gdb) where
#0  0xb7f46410 in ?? ()
#1  0xbfdd5298 in ?? ()
#2  0x00000000 in ?? ()
(gdb) thread apply all bt

Thread 16 (Thread -1214223472 (LWP 8592)):
#0  0xb7f46410 in ?? ()
#1  0xb7a05ec8 in ?? ()
#2  0x00000013 in ?? ()
#3  0x00000000 in ?? ()

Thread 11 (Thread -1240470640 (LWP 8581)):
#0  0xb7f46410 in ?? ()
#1  0xb60fdec8 in ?? ()
#2  0x00000014 in ?? ()
#3  0x00000000 in ?? ()

Thread 10 (Thread -1232077936 (LWP 8580)):
#0  0xb7f46410 in ?? ()
#1  0x00000003 in ?? ()
#2  0x00000000 in ?? ()

Thread 8 (Thread -1248863344 (LWP 8573)):
#0  0xb7f46410 in ?? ()
#1  0xb58fced8 in ?? ()
#2  0x000000de in ?? ()
#3  0x080bb684 in ?? ()
#4  0xb7ef0fab in __write_nocancel () from /lib/libpthread.so.0
#5  0x080803a6 in write_nbytes (bsock=0xb69004c0, ptr=0x80bb684 "", nbytes=222)
    at bnet.c:138
#6  0x080827ee in BSOCK::send (this=0xb69004c0) at bsock.c:292
#7  0x08082dd8 in BSOCK::despool (this=0xb69004c0,
    update_attr_spool_size=0x80783f0 <update_attr_spool_size>, tsize=2379278)
    at bsock.c:518
#8  0x08078aca in commit_attribute_spool (jcr=0x80c76c8) at spool.c:636
#9  0x080530f9 in do_append_data (jcr=0x80c76c8) at append.c:334
#10 0x080674c3 in append_data_cmd (jcr=0x80c76c8) at fd_cmds.c:194
#11 0x080670b1 in do_fd_commands (jcr=0x80c76c8) at fd_cmds.c:165
#12 0x08067612 in run_job (jcr=0x80c76c8) at fd_cmds.c:128
#13 0x08067aa4 in run_cmd (jcr=0x80c76c8) at job.c:192
#14 0x08062314 in handle_connection_request (arg=0xb69004c0) at dircmd.c:224
#15 0x0809bebc in workq_server (arg=0x80b5e60) at workq.c:357
#16 0xb7eea112 in start_thread () from /lib/libpthread.so.0
#17 0xb7be02ee in clone () from /lib/libc.so.6

Thread 3 (Thread -1222616176 (LWP 8531)):
#0  0xb7f46410 in ?? ()
#1  0xb72053a4 in ?? ()
#2  0x00000049 in ?? ()
#3  0x00000000 in ?? ()

Thread 1 (Thread -1213093008 (LWP 8526)):
#0  0xb7f46410 in ?? ()
#1  0xbfdd5298 in ?? ()
#2  0x00000000 in ?? ()
(gdb) 

Now that looks pretty broken to me as it provides no information on where the
seg fault happened, and none of my threads are at 0x00000000. If I simply ctl-c
the program half of the threads show the nonsense as you see above.  If the
program seg faults itself, the debugger shows has same problems. With the
exception of exactly how one stops the program or how it dies, the broken
debugger output is essentially the same as the information I previously sent
you in comment #4.

I can understand that you may not be able to reproduce it since your hardware
or the program you are debugging may be different, but when there are at least
3 developers telling you it is broken, I'd say there is a 99.9% chance it is
broken.  

By the way, the same problem occurs on several different computers loaded with
SuSE 10.2.  It does not occur on any other OS I have used.


-- 
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.