similar to: Using dwarf2 in kernel debug?

Hello, I can't use Wine from version >=0.9.18 anymore. It compiles ok and then it crashes somewhere in the middle of installation, I think when Wine tries to execute something. Even when I try to run winecfg it crashes. It worked with Wine version 0.9.17 and lower. Anyone have any idea what's wrong ? I'm running Slackware 10.0. Below is what happens when I try to run winecfg.

Below is from make buildworld output on FreeBSD cvsup'd to RELENG_4 (so 4.8-STABLE) on the following hardware: Intel SHG2 Hodges Dual Xeon board 2 x Intel Xeon 2.4Ghz (512k) 2 x 512MB PC-2100 266Mhz ECC DDR Seagate 36GB 10K U320 LC SCSI Adaptec SCSI Raid 2000s 48MB SDRAM Intel Hudson 3 SC5200 base w 450W Any suggestions? Cheers, Carl. <snip> cc -o make_keys -O -pipe -I.

Hi! I just installed wine 0.9.2 on my Linux system and tried installing VLC 0.8.4 for Windows: http://www.videolan.org/ The installer ran fine and VLC even started! I was able to open a WMV file but when it started playing back, it crashed: ----------------START---------------------- tom@linux:~$ wine vlc-0.8.4-win32.exe fixme:win:SetWindowTextA setting text "VideoLAN VLC media

I have a problem with an SMP 4.7 kernel with ichsmb. My BIOS has not assigned an interrupt, so the kernel does on startup: ichsmb0: <Intel 82801CA (ICH3) SMBus controller> port 0x1100-0x111f irq 0 at device 31.3 on pci0 pci_cfgintr_virgin: using routable interrupt 3 pci_cfgintr: 0:31 INTB routed to irq 3 smbus0: <System Management Bus> on ichsmb0 smb0: <SMBus general purpose

Hi ! Playing yetisports 1,2,4 and 5 works with cvs version of wine- Starting yetisports 8,7,6 and 3 fails: yetisports 8 -------------- wine: Unhandled page fault on read access to 0x02af1d74 at address 0x0000:0x00403f0e (thread 0009), starting debugger... WineDbg starting on pid 0x8 First chance exception: page fault on read access to 0x02af1d74 in 32-bit code (0x00403f0e). Register dump:

TB --- 2003-10-02 04:00:01 - starting RELENG_4 tinderbox run for alpha/alpha TB --- 2003-10-02 04:00:01 - checking out the source tree TB --- cd /home/des/tinderbox/RELENG_4/alpha/alpha TB --- /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -rRELENG_4 src TB --- 2003-10-02 04:07:38 - building world TB --- cd /home/des/tinderbox/RELENG_4/alpha/alpha/src TB --- /usr/bin/make -B buildworld >>>

TB --- 2003-07-21 05:27:28 - starting RELENG_4 tinderbox run for i386/pc98 TB --- 2003-07-21 05:27:28 - checking out the source tree TB --- cd /home/des/tinderbox/RELENG_4/i386/pc98 TB --- /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -rRELENG_4 src TB --- 2003-07-21 05:33:30 - building world TB --- cd /home/des/tinderbox/RELENG_4/i386/pc98/src TB --- /usr/bin/make -B buildworld >>>

TB --- 2003-10-02 04:44:07 - starting RELENG_4 tinderbox run for i386/i386 TB --- 2003-10-02 04:44:07 - checking out the source tree TB --- cd /home/des/tinderbox/RELENG_4/i386/i386 TB --- /usr/bin/cvs -f -R -q -d/home/ncvs update -Pd -rRELENG_4 src TB --- 2003-10-02 04:49:12 - building world TB --- cd /home/des/tinderbox/RELENG_4/i386/i386/src TB --- /usr/bin/make -B buildworld >>>

hello all, my first post so bear with me i have been lossing hair over getting black and white 2 to run on wine i finally got it down to this h4x0r@Mainframe:~/.wine/drive_c/Program Files/Lionhead Studios/Black & White 2$ wine white.exe fixme:system:SystemParametersInfoW Unimplemented action: 112 (SPI_GETMOUSESPEED) fixme:powermgnt:GetSystemPowerStatus (): stub, harmless. wine: Call from

We have a reproducible problem with FreeBSD-4.7 which is apparently a deadlock. The system is undergoing a filesystem stress test. The machine is pingable, but console and most other features are unresponsive. The console debugger can be accessed. The following information is available with db's "ps". I suspect the wchan of "inode" to be what everything is waiting on.

I've got a fix for the panic from the cd(4)/da(4) drivers when INVARIANTS is turned on in -stable. The fix is to create a task queue that runs in a thread context and use that to create the sysctl variables needed by cd(4) and da(4). The eventual fix will be to move the CAM transport layer probe code into a kernel thread. Anyway, these patches work for me, but if I could get some feedback

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ============================================================================= FreeBSD-SA-05:09.htt Security Advisory The FreeBSD Project Topic: information disclosure when using HTT Category: core Module: sys Announced:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ============================================================================= FreeBSD-SA-05:09.htt Security Advisory The FreeBSD Project Topic: information disclosure when using HTT Category: core Module: sys Announced:

[bcc: to re@] Considering the amount of changes between 4.x and 5.x, and the performance issues of the latter, I think I can safely predict that RELENG_4 will be around for a long time after the RELENG_5 branch. While I understand that some will resist making RELENG_4 any more useful than it currently is (to encourage users to move to 5.x), I think there is one issue that should be addressed: the

I've built RELENG_4 isos no problem, is there a trick to building the RELENG_4_8 isos? I am building the 'miniinst' disk - that is, with the release, docs, and a port tree, but no ports. This is so I can do a fresh install without having to update the world... I am using a script that looks like this... #!/bin/sh rm -rf /usr/obj cd /usr/src make -DNOCLEAN world kernel cd

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ============================================================================= FreeBSD-SA-05:09.htt Security Advisory The FreeBSD Project Topic: information disclosure when using HTT Category: core Module: sys Announced:

since august 8th, 2003 the kernel on my i386 pentiumIII won't compile. the problem arises in locore.s with the definition of the constants $PAGE_SHIFT and $PTESHIFT used in `shr' and `shl' instructions within the macros `fillkpt' and `fillkptphys'. i've tried to cvsup(1) RELENG_4 and RELENG_4_8 every day for over a week now, but kernel builds (as part of a buildworld)

Read the documentation on the meaning of the various 4.X tags, and am not sure what is meant by this: "The release branch for FreeBSD-4.6 and FreeBSD-4.6.2, used only for security advisories and other seriously critical fixes." Similar descriptions are used for the other RELENG_4_X tags. If I specify RELENG_4 will cvsup also include RELENG_4_3 to RELENG_4_8? Sorry folks - I'm

has anyone seen this before with 4.7-RELEASE on an SMP motherboard? It happened once on one boot, not seen it before or since on the same system. This is a 1U 2x 2.8GHz XEON system with 10 Intel 'em' devices. Programming 24 pins in IOAPIC #0 IOAPIC #0 intpin 2 -> irq 0 Programming 24 pins in IOAPIC #1 Programming 24 pins in IOAPIC #2 AP #2 (PHY# 1) failed! panic y/n? [y] ...

Hello -stable: I'm getting an error & stoppage from mergemaster in RELENG_4 (now 4.9-PRERELEASE), just updated a few minutes ago, vis: -------------------- cd /usr/src/etc/sendmail; make distribution install -o root -g wheel -m 644 /usr/src/etc/sendmail/freebsd.mc freebsd.cf /var/tmp/temproot/etc/mail install: freebsd.cf: No such file or directory *** Error code 71 Stop in