[Bug 2670] segfault on x86_64 in ia32-chroot

[Wine Bugs]

http://bugs.winehq.org/show_bug.cgi?id=2670





------- Additional Comments From kontrollator at gmx.de  2005-20-01 15:33 -------
Ok i did a gdb wine, heres the output: 
gdb wine 
GNU gdb 6.3-debian 
Copyright 2004 Free Software Foundation, Inc. 
GDB is free software, covered by the GNU General Public License, and you are 
welcome to change it and/or distribute copies of it under certain conditions. 
Type "show copying" to see the conditions. 
There is absolutely no warranty for GDB.  Type "show warranty" for details. 
This GDB was configured as "i386-linux"...(no debugging symbols found) 
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". 
 
(gdb) r 
Starting program: /usr/bin/wine 
 
Message from syslogd at rockerduck at Thu Jan 20 22:37:01 2005 ... 
rockerduck kernel: invalid operand: 0000 [1] 
Speicherzugriffsfehler 
 
And the output of dmesg: 
----------- [cut here ] --------- [please bite here ] --------- 
Kernel BUG at memory:746 
invalid operand: 0000 [1] 
CPU 0 
Modules linked in: ipt_TCPMSS ipt_tcpmss pppoe pppox af_packet ppp_generic 
slhc md5 ipv6 ipt_MASQUERADE ipt_state iptable_mangle iptable_filter ipt_ECN 
ipt_ecn ip_nat_ftp ip_conntrack_ftp ip_nat_irc ip_conntrack_irc ipt_conntrack 
ipt_multip ort iptable_nat ip_conntrack ip_tables usblp usbhid snd_via82xx 
snd_ac97_codec s nd_mpu401_uart snd_rawmidi snd_seq_device ehci_hcd eth1394 
uhci_hcd usbcore sata _via ohci1394 r8169 crc32 tuner bttv video_buf 
firmware_class i2c_algo_bit v4l2_ common btcx_risc videodev floppy evdev xfs 
ext3 jbd mbcache sg pata_pdc2027x sat a_promise libata ntfs snd_rtctimer rtc 
snd_ioctl32 snd_pcm_oss snd_mixer_oss snd _pcm snd_timer snd soundcore 
snd_page_alloc binfmt_misc w83627hf eeprom i2c_sens or i2c_isa i2c_viapro 
i2c_core sd_mod sr_mod sbp2 scsi_mod ieee1394 ide_cd cdrom  unix 
Pid: 6399, comm: gdb Not tainted 2.6.10-ck5 
RIP: 0010:[<ffffffff8015d6b7>] [<ffffffff8015d6b7>] 
RSP: 0018:0000010004c0fe58  EFLAGS: 00010246 
RAX: 0000000000000000 RBX: 0000000000000ff0 RCX: 000ffffffffff000 
RDX: 0000010000000000 RSI: ffffffff802f90c0 RDI: 000001000615a140 
RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000010 
R10: 0000010004c0e000 R11: 0000000000000293 R12: 000001000615a140 
R13: 0000000000000000 R14: 00000100053dd070 R15: 0000000000000000 
FS:  0000002a9558b6b0(0000) GS:ffffffff80363cc0(005b) knlGS:000000005573e080 
CS:  0010 DS: 002b ES: 002b CR0: 000000008005003b 
CR2: 00000000081b3820 CR3: 0000000000101000 CR4: 00000000000006e0 
Process gdb (pid: 6399, threadinfo 0000010004c0e000, task 00000100053dd710) 
Stack: 00000000000000d0 0000000000003950 037ffffc7e403950 000001000615a1a8 
       0000000100000010 00000000ffffe000 0000000100000014 0000010004c0ff08 
       0000000000000000 0000000000000004 
Call Trace:[<ffffffff80138ec9>] [<ffffffff80180d82>] [<ffffffff8012c980>] 
       [<ffffffff801208e3>] 
 
Code: 0f 0b 11 08 2c 80 ff ff ff ff ea 02 48 83 7c 24 70 00 74 38 
RIP [<ffffffff8015d6b7>] RSP <0000010004c0fe58> 
 
What does this mean ? Is it indeed a kernel-bug ? What should i do next ? 
 
Greetings Jan 

-- 
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.