similar to: segfault in current cvs

Displaying 20 results from an estimated 200 matches similar to: "segfault in current cvs"

2020 Apr 21
2
[PATCH] nouveau/hmm: fix nouveau_dmem_chunk allocations
In nouveau_dmem_init(), a number of struct nouveau_dmem_chunk are allocated and put on the dmem->chunk_empty list. Then in nouveau_dmem_pages_alloc(), a nouveau_dmem_chunk is removed from the list and GPU memory is allocated. However, the nouveau_dmem_chunk is never removed from the chunk_empty list nor placed on the chunk_free or chunk_full lists. This results in only one chunk ever being
2003 Aug 09
3
CVS/test version config/build failures on FreeBSD
While diagnosing a problem I was having with IMAP and SSL (which I ended up fixing by simply upgrading from 0.99.9.1 to 0.99.10, and possibly affected by upgrading openssl libs from 0.9.7a to 0.9.7.b), I attempted to try the CVS version of Dovecot. When using the CVS version, apparently I have to first generate 'configure' using autogen.sh (?). This was the result of that, on FreeBSD
2004 Aug 06
1
installing ices2 (fwd)
Any ideas please. I want to get this installed! I have the Latest CVS download! okay I am having some difficulty getting ices2 installed on freebsd this happens during execution of autogen.sh --- snip --- checking whether ln -s works... yes loading cache /dev/null within ltconfig ltconfig: you must specify a host type if you use `--no-verify' Try `ltconfig --help' for more
2003 Apr 01
4
compile error
Hello, I hope this is the place to bug ppl about compile errors. So here I go. I downloaded the latest through CVS last night and ran ./autogen.sh according to the manual and ran into the following error. Does anyone happen to have a fix for it? I am on FreeBSD 4.6 Stable. Thanks in advance, Till << ./autogen.sh output and error message >> elation# ./autogen.sh I am going to run
2004 Sep 10
5
Re: beta 10 candidate checked in
> > > $ aclocal && autoconf && automake -c -a -i > > > aclocal: configure.in: 45: macro `AM_PATH_XMMS' not found in > library > > > > my hunch is that your version of either automake or possibly > > autoconf is not recent enough. > > No. He simply doesn't have xmms installed. That's what I mentioned > a while ago:
2004 Aug 06
1
error compiling from CVS
Hi all, Don't ask me why but I had to recompile icecast (from CVS) and now I'm getting this: #./configure checking for a BSD compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking whether make sets ${MAKE}... yes checking for working aclocal-1.4... found checking for working autoconf... found checking for working automake-1.4... found
2001 Jul 02
0
ReleaseLargeFreeVectors SIGSEGV (?) (PR#1008)
Full_Name: Roger Bivand Version: 1.3.0 OS: GNU/Linux RH6.2, 7.0, Debian 2.2 Submission from: (NULL) (158.37.100.64) I'm working on interfacing ANN: A Library for Approximate Nearest Neighbor Searching (http://www.cs.umd.edu/~mount/ANN/) to R, following up a prototype package I tried in May 2000. ANN is written in C++; my C++ is very weak. Last year I didn't experience any problems with
2000 Dec 22
1
vorbis/ltconfig
The file vorbis/ltconfig appears to be checked into CVS. This is an automatically generated file -- it should not be under CVS control. {+} Jeff Squyres {+} squyres@cse.nd.edu {+} Perpetual Obsessive Notre Dame Student Craving Utter Madness {+} "I came to ND for 4 years and ended up staying for a decade" --- >8 ---- List archives: http://www.xiph.org/archives/ Ogg project
2003 Sep 17
0
Fwd: [Full-Disclosure] Sendmail 8.12.9 prescan bug (a new one) [CAN-2003-0694]
More patch-o-rama :-( ---Mike >From: Michal Zalewski <lcamtuf@dione.ids.pl> >To: bugtraq@securityfocus.com, <vulnwatch@securityfocus.com>, > <full-disclosure@netsys.com> >X-Nmymbofr: Nir Orb Buk >Subject: [Full-Disclosure] Sendmail 8.12.9 prescan bug (a new one) >[CAN-2003-0694] >Sender: full-disclosure-admin@lists.netsys.com >X-BeenThere:
2002 Jul 27
2
trouble compiling vorbis 1.0 on openbsd
Compiled libbogg and libao using ./configure; make Then moved to libvorbis source folder Installed libtool (1.3.5p3), autoconf (2.52) and automake (1.4-p5). gnu make is also there (3.79.1) i had to create a link for autoconf as after install it was installed as /usr/local/bin/autoconf-new so i added a link from it to /usr/local/bin/autoconf output from ./autogen is: -- $ ./autogen.sh
2019 Mar 21
0
Nouveau dmem NULL Pointer deref (SVM)
On Thu, Mar 21, 2019 at 04:59:14PM +0100, Tobias Klausmann wrote: > Hi, > > just for your information and maybe for some help: with 5.1rc1 and SVM > enabled i see the following backtrace [1] when the nouveau card (reverse > prime) goes to sleep, for now i have papered over with [2] which leaves me > with userspace hangs. Any pointers where to look for the actual culprit? >
2001 Jul 03
0
(PR#1008) SIGSEGV under 1.1.1 too
It looks as though the problem isn't in R - I provoked a SIGSEGV under R 1.1.1 on RH62: > for (i in 1:100) an1 <- ann(cbind(runif(1000), runif(1000)), k = 4) > for (i in 1:100) an1 <- ann(cbind(runif(1001), runif(1001)), k = 4) Program received signal SIGSEGV, Segmentation fault. 0x40111109 in chunk_free (ar_ptr=0x401a5d40, p=0x8849a30) at malloc.c:3111 3111 malloc.c: No such
2001 Oct 03
1
segmentation violation using openssh-2.9.9p2 on linux 2.2.19
I received a segmentation violation whilst using openssh-2.2.9p2 today: Kernel 2.2.19-6.2.7 (Redhat 6.2) Gcc version egcs-2.91.66 glibc-2.1.3-22 Hardware is 333MHz K6-3Dnow with 64MB RAM if that matters Here is what happened along with a stack dump... # ssh -L 80:someplace.net:80 -l charlie someplace.net Password: (works for a while, then seems to freeze) ^C Segmentation violation (core
2002 Jul 10
2
cvs: debian updates and autogen.sh trouble
Hello, I couldn't help noticing that the debian build system in cvs was changed. As I used to compile and install from cvs, I discovered a small problem regarding autogen.sh. It's called in debian/rules, before the obj-dir is created (and changed into and ../configure is started). At least on my system autogen.sh implicitly runs ./configure, so the original source path is already
2000 Apr 17
0
exhaustion and cores
Hello, trying to start tinc I get the following at the client: Apr 17 16:34:50 otto tincd[10238]: tincd 0.3.3 starting, debug level 1. Apr 17 16:34:50 otto tincd[10238]: Generating 128 bits keys. Apr 17 16:34:50 otto tincd[10238]: Ready: listening on port 655. Apr 17 16:34:50 otto tincd[10238]: Connected to xxx Apr 17 16:34:50 otto tincd[10238]: Memory exhausted; exiting. - on a machine with 80
2004 Sep 10
2
flac-1.0.3_beta released
On Tue, 11 Jun 2002 11:51:33 +0400 Andrey Astafiev <andrei@tvcell.ru> wrote: > flac-1.0.3_beta compilation breaks for me with message: I had the same experience, too. I think that a cause is in configure and configure.in files. Therefore, let's rebuild these files. I took the following, and solved the problem. $ cd flac-1.0.3_beta $ automake $ autoconf $ ./configure ;make --
2001 Jan 26
1
[fwd] Ogg123 crash report on EV4 Multia
----- Forwarded message from Telford Tendys <telford@triode.net.au> ----- Delivery-Date: Thu Jan 25 22:22:57 2001 Date: Fri, 26 Jan 2001 16:26:27 +1100 From: Telford Tendys <telford@triode.net.au> To: feedback@vorbis.com Subject: Comments on your code User-Agent: Mutt/1.2.5i Dear Vorbis, I didn't even know about ogg or vorbis until I was at a conference and someone said, ``if
2000 Jun 23
1
MAINLD and SHLIBLD
I would like to always use ${CC} for linking the main binary and the shlibs. Inspection of configure.in reveals that we currently deviate in the following cases: mainld shlibld aix[2-9]* ld ld alpha*osf* ${FC} -g -nofor_main -fpe3 ${FC} hpux* ${CC} ld Does anyone recall why we do not use ${CC} in these cases? Did anyone successfully build R on these platforms with ${CC} for
2020 Apr 23
0
[PATCH] nouveau/hmm: fix nouveau_dmem_chunk allocations
On Tue, Apr 21, 2020 at 04:11:07PM -0700, Ralph Campbell wrote: > In nouveau_dmem_init(), a number of struct nouveau_dmem_chunk are allocated > and put on the dmem->chunk_empty list. Then in nouveau_dmem_pages_alloc(), > a nouveau_dmem_chunk is removed from the list and GPU memory is allocated. > However, the nouveau_dmem_chunk is never removed from the chunk_empty > list nor
2001 Jan 19
0
sshd crashes (w/ skey)
Hi! There is a situation when sshd will crash, but it might be rather hard to reproduce. I'll try to explain the setup :) S/KEY is compiled and installed (taken from http://www.sparc.spb.su/solaris/skey/ ) on Linux box (kernel 2.4.0). Then, OpenSSH 2.3.0p1 is compiled with skey support. It all works fine (patch has been applied too, which fixes skey issue found in November). Now, for the