search for: buggier

I don't know if it's just me or if there is an issue in wine, but HL seems to be getting buggier with every release. I've been having issues with the loading screen since 20010629, but when I moved to 20010824 things just got bad, I get a crash after trying to join a second game (play one, exit, join another). It's an actual bug in the code too, I believe it was a buffer error but I wa...

...ealize it doesn't return. That's because the declaration of abort() is decorated with __attribute__((__noreturn__)). So is GCC smarter than VC++? As it turns out, in VC++ the declaration of abort() is decorated with __declspec(noreturn). Whidbey is not stricter than 2003, it is merely buggier. VC++ has always complained about functions failing to return a value; this is not new in Whidbey. What is new is that it no longer pays attention to __declspec(noreturn). That is why it is difficult to justify supporting Whidbey. This bug may have been easy to work around. The next one ma...

.... That's because the > declaration of abort() is decorated with __attribute__((__noreturn__)). > > So is GCC smarter than VC++? As it turns out, in VC++ the declaration of > abort() is decorated with __declspec(noreturn). > > Whidbey is not stricter than 2003, it is merely buggier. VC++ has always > complained about functions failing to return a value; this is not new in > Whidbey. What is new is that it no longer pays attention to > __declspec(noreturn). Got by a Microsoft bug, sorry about that folks. I should have looked at abort()'s declaration. >...

...l RAID boxes: Infortrend I never will go for cheepy fake RAID (adaptec is one off the top of my head). Also, it was not my choice but I had to deal with Hm... not good external RAID boxes: by Promise, and by Raid.com to mention two. You are implying that firmware of hardware RAID cards is somehow buggier than software of software RAID plus Linux kernel (sorry if I misinterpreted your point). I disagree: embedded system of RAID card and RAID function they have to fulfill are much simpler than everything involved into software RAID. Therefore, with the same effort invested, firmware of (good) hardwar...

Icecast2 compiles on OpenBSD 3.2 with the steps outlined by Moritz (thanks for that). I'm running into problems streaming ogg files from the fileserve directory, although serving mp3 files from the same directory happens without a hitch...again, both work fine on a Debian system. I'll try building the ogg and vorbis libraries from source to see if that fixes anything (they are

...h files) > [2003-03-26 16:31:15] DBUG connection/_handle_get_request Client connected > These logs suggests that everything is working perfectly. I suspect your client is broken (winamp3 is widely considered to be a steaming heap of... well, something - and for good reason, it's vastly buggier than 2.x) Mike --- >8 ---- List archives: http://www.xiph.org/archives/ icecast project homepage: http://www.icecast.org/ To unsubscribe from this list, send a message to 'icecast-request@xiph.org' containing only the word 'unsubscribe' in the body. No subject is needed. Unsu...

Peter Bartke wrote: > Im hesitating doing a BIOS upgrade for the ASUS P5GD2 motherboard, some > years ago I got an unusable board from this procedure, but this was > another company. Afterwards I stayed away from doing this, seemed not be > worth the trouble and the result could be buggier than the older one. > What is your experience now, is it safe? My experience is that you generally want to upgrade your BIOS if you have problems, but not otherwise. The good news is that many BIOSes have the option to roll back a BIOS upgrade if needed (read out the old BIOS to a file fr...

I installed Komposer from .tgz file, since I couldn't find it on any of my repos. It wants to use libpangocairo, but I can't find anywhere willing to give it to me. I did a yum provides libpangocairo, but nobody would own up to having it. Is there somewhere I can download a compatible .rpm? Is there somewhere I can rpm a compatible libpangocairo? Thanks, Ted Miller Indiana

Aaron Gray wrote:- > Hi, > > I have built yesterdays CVS download of LLVM on Whidbey (Microsoft Visual Studio 2005). > > LLVM built with trivial mods due to VS strictness compared to GCC. Basically there are missing return statement/values where Abort() is called, I replaced these with dummy constructors to get them to compile. Sounds like GCC is smart enough to realise it

Hi, I'm using CentOS 5.3 on all my desktops, and I really like it. Now I'd like to build a few additional apps that aren't included in any third party repo. Some of them require GTK2 2.12 to build, so I'm considering a (careful) upgrade of this package. General question: 1) how "safe" is it to upgrade this package? To do so, I'd use an SRPM from Fedora. 2) What

My primary use for Wine is to run an application called Doom Builder 1.86. It's a GUI-based level editor for the 1994 id Software game Doom. It is available at http://www.doombuilder.com/ In Wine versions 1.3.28 and below this has always run without major problems, the only "workarounds" being to put msvbsm60.dll and oleaut32.dll in the program folder, and set oleaut32 native in

...s me of Microsoft Office's infamous Clippy and > expects me to jump through burning loops to configure the system as I want > it. What you're describing is what kickstart is for. That's flexible and fairly bug free. GUI installers, the more complex you make them (flexibility) the buggier they are. Fedora Atomic, one possible way of the future without any installer. Atomic updates, and rollback and rollfoward. http://www.projectatomic.io/ And another using btrfs send/receive images (not mentioned but could instead use seed devices): http://0pointer.net/blog/revisiting-how-we-put-t...

Hi, I have built yesterdays CVS download of LLVM on Whidbey (Microsoft Visual Studio 2005). LLVM built with trivial mods due to VS strictness compared to GCC. Basically there are missing return statement/values where Abort() is called, I replaced these with dummy constructors to get them to compile. I do not have 2003. 2005 is much stricter than 2003 and there are quite alot of warnings on

I have released SYSLINUX 2.06; it's basically identical to 2.06-pre4. I'm doing this now because the bug fixes are so major and because I am not sure I'll be around next week. -hpa 2.06 is a bug fix release. Changes in 2.06: * ALL: Fix problem that would occationally cause a boot failure, depending on the length of the kernel. * ISOLINUX: Fix problem

Le 19/02/2015 05:43, Chris Murphy a ?crit : > My personal view on installers is extremely biased toward the user > staying out of trouble, they shouldn't have to read documentation for > a GUI installer. A *user* never has to even see - or use - an installer. A USER has to USE a computer, by which I mean the applications he or she needs to get some work done. The person who gets

...gt; > Getting all this done for Fedora 9 is seriously ambitious, but it is the only > long term sustainable option, other than dropping Xen entirely. > > What this means though, is that Fedora 9 Xen will certainly be going through > periods of instability and will certainly be even buggier than normal. F9 > may well end up lacking features compared to Xen in Fedora 8 & earlier (eg no > PCI device passthrough, or CPU hotplug). On the plus side though we will be > 100% back in sync with bare metal kernel versions & hopefully even have a > lot of this stuff merged in...

...e landing as well. I certainly understand what you're saying, but, as you point out, many of these are existing bugs that are being exposed by other changes (and they're seemingly all over the map). My general feeling is that the more limited the applicability of a particular transform the buggier it will tend to be. The work here to allow vectorization of an every-wider set of inputs will really help to expose, and thus help us eliminate, bugs. As such, one of the largest benefits of adding the function-vectorization work (https://reviews.llvm.org/D22792), and outer-loop vectorization capab...

On Zed''s suggestion, I caught two new spinning mongrels and sent a SIGUSR2. The code appears to be stuck in read_multipart for both processes: # kill -USR2 6109 ** USR2 signal received. Thu Sep 21 14:55:39 EDT 2006: Reaping 1 threads for slow workers because of ''shutdown'' Thread #<Thread:0x419d7ce0 run> is too old, killing. Waiting for 1 requests to finish, could

On Fri, February 27, 2015 10:00 pm, Marko Vojinovic wrote: > On Fri, 27 Feb 2015 19:24:57 -0800 > John R Pierce <pierce at hogranch.com> wrote: >> On 2/27/2015 4:52 PM, Khemara Lyn wrote: >> > >> > What is the right way to recover the remaining PVs left? >> >> take a filing cabinet packed full of 10s of 1000s of files of 100s of >> pages each,

...e >> declaration of abort() is decorated with __attribute__((__noreturn__)). >> >> So is GCC smarter than VC++? As it turns out, in VC++ the >> declaration of abort() is decorated with __declspec(noreturn). >> >> Whidbey is not stricter than 2003, it is merely buggier. VC++ has >> always complained about functions failing to return a value; this is >> not new in Whidbey. What is new is that it no longer pays attention >> to __declspec(noreturn). > > > Got by a Microsoft bug, sorry about that folks. I should have looked > at ab...