similar to: icecast2 alpha 1 (09/19/03) seg fault

Displaying 20 results from an estimated 300 matches similar to: "icecast2 alpha 1 (09/19/03) seg fault"

2011 May 19
1
Can't install Microsoft Data Access Components
I am trying to run the program Bioedit in a Mac OS X 10.6.7. I have Wine+Winebottler 1.1.44 and Wineskin Winery 1.1. I can install Bioedit without problems, but when I try to run it this appears: Error creating object. Please verify that the Microsoft Data Access Components 2.1 (or later) have been properly installed. So I downloaded MDAC v2.81 from CNET (couldn't get it from Microsoft) and
2006 Mar 02
0
Lancer 20060302 is out
Lancer 20060302 (based on aoTuV 4.51) http://homepage3.nifty.com/blacksword/ Changes: * update to oggenc v2.81 * optimized SSE2 code implementation * bark_noise_hybridmp and seed_curve are inline assembled * modified mdct_forward's SSE optimization * double step bresebham algorithm for render_line, render_line0 implementation
2007 Jun 04
0
Seg fault ferret-browser
Hello, Getting a seg fault with 0.11.4 /var/lib/gems/1.8/gems/ferret-0.11.4/lib/ferret/browser.rb:226: [BUG] Segmentation fault ruby 1.8.5 (2006-08-25) [i486-linux] Maybe this a known issue but I thought that I better report it. Cheers, henke
2006 Oct 16
0
seg fault, ferret 0.10.11
Hi, we''re using Ferret 0.10.11 with acts_as_ferret (stable from svn), on a unix box, running rails 1.1.6 in production. a few days ago i rebuilt the index (by deleting the previous one and letting acts_as_ferret do its thing), and it ran fine for a few days. this evening i got a seg fault when one of the indexes was being updated via aaf, and now all ferret searches are busted,
2006 Sep 27
2
Seg Fault - crashed our server
We were using ferret (with acts_as_ferret) on our production boxes. Everything was going OK for a few days then we got a seg fault from it that brought down the box. The specs: * Rails 1.1.6 * Ruby 1.8.4 * Ferret 0.10.6 * RedHat ES 3 * Apache * Pound * 5 instances of Mongrel Can ferret handle multiple processes accessing it''s files at the same time? Not that we were doing this (but
2005 Mar 22
0
RE: etc win32utils seg faults when a pdc/bdc is queried
> -----Original Message----- > From: "Pe?a, Botp" [mailto:botp@delmonte-phil.com] > Sent: Tuesday, March 22, 2005 12:19 AM > To: ruby-talk ML > Subject: Re: etc win32utils seg faults when a pdc/bdc is queried > > > Hi Win32 team, > > Etc seg faults when a pdc or bdc (domain controller) is > queried. Is support for domain controllers not up yet? >
2008 Dec 02
0
4gb seg fixup errors
Hi, I am running Debian etch on dom0. I want to run debian unstable on one DomU, but I keep getting 4gb seg fixup errors, presumably because the libc6-xen installed there is much newer than on Dom0 (or perhaps there is some bug with Xen and libc6-xen version 2.7-16). I have two questions; 1. Why does the libc version on Dom0 matter at all for DomU (if that is the case)? As far as I've read,
2007 Apr 18
0
[PATCH 3/21] i386 Apm seg in gdt
Since APM BIOS segment limits are now fixed, set them in head.S GDT and don't use the complicated _set_limit() macro expansion. Signed-off-by: Zachary Amsden <zach@vmware.com> Index: linux-2.6.14-zach-work/arch/i386/kernel/head.S =================================================================== --- linux-2.6.14-zach-work.orig/arch/i386/kernel/head.S 2005-11-04 15:46:11.000000000 -0800
2007 Apr 10
0
rake test:functionals seg fault
Hello, I get a segfault since I''ve updated my system (to rails 1.2.2 and rake 0.7.2) when running rake:functionals I''ve tried to run each individual test, none of them produced a seg fault. Ruby version is 1.8.4 (CentOS, the OS I''m using don''t provide an official 1.8.6 release) Thanks -- Posted via http://www.ruby-forum.com/.
2007 Mar 10
0
Re: 4gb seg fixup errors fc6
It is a quite "old" post but the same error at debian etch mv /lib/tls /lib/tls.disable <--- at the vm helped to avoid those messages mfg matthias old mail: Hi. I recently upgraded to fc6. I''m using the fc6 supplied xen packages. However, now all my VM''s are logging entries like: 4gb seg fixup, process sshd (pid 1162), cs:ip 73:008d8cfc printk: 185714 messages
2012 Jul 03
0
Puppet v2.7.11 Seg Faults
Hello, Migrating some clients from an ancient client to a new infrastructure based on 2.7.11 these are RHEL boxes Some clients are hitting an issue [30/06/12 05:11:37 UTC] /usr/lib/ruby/site_ruby/1.8/puppet/util/settings.rb:733: [BUG] Segmentation fault [30/06/12 05:11:37 UTC] ruby 1.8.5 (2006-08-25) [x86_64-linux] [30/06/12 05:11:37 UTC] [30/06/12 05:11:37 UTC] Puppet SSL run return
2006 Dec 05
0
4gb seg fixup messages on fc6 DomU, echo "hwcap 0 segneg" > /etc/ld.so.conf.d/libc6-xen.conf doesn''t work
Hi, I am using the kernel-2849 src rpm to compile a pae DomU, but i get a lot of printks and the DomU doesn''t give me a shell (just goes on printing 4gb seg fixup messages). My DomU kernel is 2.6.18-prep and it looks like i have the right libraries in /lib/nosegneg. any suggestions? regards, radhesh _______________________________________________ Xen-users mailing list
2006 Jun 28
1
compiz aiglx fbconfig-depth-fix seg-fault
glXGetVisualFromFBConfig(dpy, fbConfigs[j]) returns a null pointer I'm up to date on drm, mesa, xserver and ati driver. Compiz seems to work fine, though, if I just don't apply the fbconfig-depth-fix patch. I'm not sure if I'm missing anything, though, because I'm not running gnome and obviously some of the effects won't work. I get nothing without Kristian's
2007 Apr 18
0
[PATCH 3/21] i386 Apm seg in gdt
Since APM BIOS segment limits are now fixed, set them in head.S GDT and don't use the complicated _set_limit() macro expansion. Signed-off-by: Zachary Amsden <zach@vmware.com> Index: linux-2.6.14-zach-work/arch/i386/kernel/head.S =================================================================== --- linux-2.6.14-zach-work.orig/arch/i386/kernel/head.S 2005-11-04 15:46:11.000000000 -0800
2006 Feb 11
2
[LLVMdev] hello. seg faults on AMD64 linux
Hello, I've installed LVM 1.6 and followed the getting started instructions and lli hello.bc works fine but when I convert it to hello.native it seg faults. AMD64 machine uname -a: Linux hp5kuw 2.6.12-10-amd64-k8 # Mon Jan 16 17:23:13 UTC 2006 x86_64 GNU/Linux llvm-gcc --version outputs: llvm-gcc (GCC) 3.4-llvm 20051104 (LLVM 1.6) What have I done wrong? Wink Saville
2006 Feb 11
0
[LLVMdev] hello. seg faults on AMD64 linux
There is no x86_64 code generator at this time. Wink Saville wrote: > Hello, > > I've installed LVM 1.6 and followed the getting started instructions > and lli hello.bc works fine but when I convert it to hello.native it > seg faults. > > AMD64 machine uname -a: > > Linux hp5kuw 2.6.12-10-amd64-k8 # Mon Jan 16 17:23:13 UTC 2006 > x86_64 GNU/Linux > >
2007 Jul 21
1
[LLVMdev] Seg faulting on vector ops
On 21/07/2007 23:51:28, Chris Lattner (sabre at nondot.org) wrote: > Evan's solution is the right one. However, your code is valid, so it > shouldn't > crash. I think it dies because linux does not guarantee that > the stack is 16 byte aligned, and the vector operations expect this. The > code generator should compensate and dynamically align the stack on entry >
2010 Oct 25
0
[LLVMdev] DebugInfo: seg fault
Hi, I wanted to print the contents of a DICompileUnit object but encountered a segmentation fault after invoking dump()/print method. Here is the code snippet ... unsigned DW_LANG_XXX = 0x8001; llvm::StringRef filename("l8.cpp"); llvm::StringRef dir("/home/cfiles"); const char* producer = "Group";
2011 Sep 19
1
[LLVMdev] Seg Fault when creating an execution engine
I am creating an ExecutionEngine using the LLVMCreateExecutionEngineForModule function from the C API. I am get a set fault with the following backtrace. Program received signal EXC_BAD_ACCESS, Could not access memory. Reason: KERN_INVALID_ADDRESS at address: 0x0000000000000120 0x0000000107c06643 in llvm::LLVMTargetMachine::addCommonCodeGenPasses () (gdb) bt #0 0x0000000107c06643 in
2012 Mar 21
0
[LLVMdev] llvm seg fault when specifying addRequiredTransitive in module pass
Hi all, I am using llvm to perform some static analysis with a module pass. In getAnalysisUsage(), I specified some required passes by: addRequiredTransitive<LoopInfo>(); When I run my pass using opt, it crashes with segmentation fault with callstack: #0 0x0877aebd in llvm::PMTopLevelManager::findAnalysisUsage (this=0x8c10934, P=0xb15b988) at PassManager.cpp:573 #1 0x0877aa9b in