Displaying 20 results from an estimated 1176 matches for "sigsegvs".
Did you mean:
sigsegv
2012 Oct 26
1
[LLVMdev] VMKit compilation error
Hi,
I have a problem with compiling the new revision, the file Sifsegv_gc makes
a call to the file Sigsegv.cpp but returns as file already allocated:
...
llvm [3]: Compiling for Debug + Asserts Sigsegv.cpp build (bytecode)
llvm [3]: Compiling Sigsegv.ll to Sigsegv.bc for Debug + Asserts build (
bytecode)
llvm [3]: Compiling Sigsegv.bc to Sigsegv.s for Debug + Asserts build
llvm [3]: Compiling for
2014 Sep 18
2
SIGSEGV on CentOS6
We're been running the distribution version of Samba 3.6.9 as DC on Centos
6 for a few weeks now with a number of Samba 4 clients. We have ~20,000
machine and user accounts in our password database.
We see a SIGSEGV every 24-48 hours or so in tcopy_passwd.
I built a Samba 3.6.24 with debugging symbols and waited for a core file
which we got this morning.
Looking through the code we can
2010 Nov 19
3
[LLVMdev] : SIGSEGV in compiled programs during stack unwinding
It seemed I found possible llvm-g++ bug.
Programs compiled with llvm-g++ 4.5 crashed with SIGSEGV during stack
unwinding in such testcase:
chaos at chaos-desktop ~ % g++ --version
g++ (Ubuntu/Linaro 4.5.1-7ubuntu2) 4.5.1
chaos at chaos-desktop ~ % echo "struct X{ ~X(){} }; int main() { X x; throw 1;
}" > test.cpp && g++ test.cpp && ./a.out
terminate called after
2004 Jun 29
1
seg fault using ocfstool
Hi all,
i have the following configuration:
RHAS 2.1 2.4.9-e.40enterprise #1 SMP (2 node cluster).
ocfs-support-1.1.2-1
ocfs-tools-1.1.2-1
ocfs-2.4.9-e-enterprise-1.0.12-1
i followed the users guide to install and configure ocfs.
During definition and formatting of ocfs-partitions the ocfstool crashed.
Now restarting ocfstool fails with the following error:
ocfstool
Abnormal termination!
2009 May 24
1
[Bug 21908] New: SIGSEGV when no kernel DRM present
http://bugs.freedesktop.org/show_bug.cgi?id=21908
Summary: SIGSEGV when no kernel DRM present
Product: xorg
Version: unspecified
Platform: x86 (IA32)
OS/Version: Linux (All)
Status: NEW
Severity: major
Priority: medium
Component: Driver/nouveau
AssignedTo: nouveau at lists.freedesktop.org
2001 Dec 12
1
2.5.0, Solaris 2.6, Daemon SIGSEGV
Hello,
I have compiled rsync 2.5.0 cleanly on a Solaris 2.6 box, and can use the resultant binary as a client with no problem. However, when I try and start a daemon, it exits with exit code 0, and no daemon running.
I have previously run 2.4.6 and other versions with the same rsyncd.conf file, but can't seem to get the daemon up with 2.5.0. A truss shows the following:
# truss -f
2013 Dec 04
3
[Bug 881] New: SIGSEGV on startup
https://bugzilla.netfilter.org/show_bug.cgi?id=881
Summary: SIGSEGV on startup
Product: nftables
Version: unspecified
Platform: x86_64
OS/Version: All
Status: NEW
Severity: enhancement
Priority: P5
Component: nft
AssignedTo: pablo at netfilter.org
ReportedBy: shawn at churchofgit.com
2007 Nov 17
2
SIGSEGV (Segmentation fault) with antispam plugin
Hi all.
I am trying to get dovecot (1.0.rc17) running with antispam plugin.
I have created another backend, which executes "sa-learn" from
spamassassin's arsenal. The backend is modeled after sendmail backend.
But I can't seem to get the plugin working wit either my backend or
signature-log.
This is my ".config":
DOVECOT=/usr/src/dovecot-1.0.7
DOVECOT_VERSION=1.0
2010 Nov 20
0
[LLVMdev] : SIGSEGV in compiled programs during stack unwinding
Hi Chaos A.D.,
> It seemed I found possible llvm-g++ bug.
> Programs compiled with llvm-g++ 4.5 crashed with SIGSEGV during stack unwinding
> in such testcase:
I can reproduce this - investigating.
Ciao,
Duncan.
2005 Nov 15
0
process imap SIGSEGVs when getting STATUS on mbox box
Hi,
I just added an "archive" mbox namespace to my dovecot setup, so that
people can put their old mail into a slightly more inode-friendly
box. When querying the STATUS on one of these boxes, I got a sigsegv:
Program received signal SIGSEGV, Segmentation fault.
0x0000000000454d24 in message_parse_header_next (ctx=0x59e500, hdr_r=0x7fbffff420) at message-parser.c:759
759
2009 Sep 10
1
SIGSEGV at kickstart
Hi! I have a problem that i dont know how to tackle ...
i have done kickstarting many times but know it seems i hit an wall ...
i try to kickstart through nfs an 64 bit centos .. just after taking ip
trough dhcp i receive an SIGSEGV ! i dont know what to do anymore as the
same ks.cfg worked very well until now ..
Many thanks!
Adrian
-------------- next part --------------
A non-text attachment
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
2003 Nov 17
1
rsync --daemon and logfile that can't be created
If the rsyncd.conf has a line such as:
log file = /var/log/rsync/log
and /var/log/rsync doesn't exist or isn't a directory (or the log file
can't be opened for any other reason), then there's no warning
whatsoever, as rsync forks itself into the background before checking
the config, opening the log file, etc.
Worse still, it gets a SIGSEGV, and dumps core. Here's a strace
2017 Oct 17
3
[Bug 1190] New: adding element to map with stateful object and flag interval raise SIGSEGV
https://bugzilla.netfilter.org/show_bug.cgi?id=1190
Bug ID: 1190
Summary: adding element to map with stateful object and flag
interval raise SIGSEGV
Product: nftables
Version: unspecified
Hardware: x86_64
OS: All
Status: NEW
Severity: normal
Priority: P5
Component:
2007 Sep 07
2
Problems in x86_64 Centos 5
We upgraded a 64 bit server from Centos 4 to 5 and encountered some
strange problems. Tcsh segfaulted irregurarily and emacs gave irregurarily
strange error messages about regular expressions. Both problems
disappeared when a 32-bit version was installed instead of the 64-bit.
Ldconfig still occasionally segfaults.
64-bit servers where Centos 5 was installed from scratch have no problems.
It is
2005 Dec 21
1
ustack() issues && correlating SIGSEGV activity?
Howdy,
I was playing around with the malloc/free D script provided by
Philip Beevers:
http://www.opensolaris.org/jive/thread.jspa?threadID=4224&tstart=15
And decided to change the free:entry probe from:
pid24169::free:entry
/ sz[arg0] /
{
printf("Freeing %p (size %d)\n", arg0, sz[arg0]);
sz[arg0] = 0;
}
to:
pid24169::free:entry
/ ! sz[arg0] /
{
printf("[ *
2008 Oct 01
5
ustack()s of SIGSEGV''ed programs
Hi all,
I am trying to write a D script which would print ustack() for every
program in the system receiving SIGSEGV. All the stacks printed in
trap()/sigtoproc() context do not have meaningful symbols.
The following solves the problem to some degree but I''d much rather have
a self-contained D script.
dtrace -w -n ''fbt:genunix:sigtoproc:entry/arg2 == 11/ {
2003 May 24
2
winamp3 segfaults wine?
hi there, installation of winamp3 ran successfully. but running winamp3.exe
throws sigsegv at me..
(gdb) r winamp3.exe
Starting program: /usr/bin/wine winamp3.exe
[New Thread 16384 (LWP 24073)]
Xlib: extension "XFree86-DRI" missing on display ":0.0".
err:win32:_EnterSysLevel (0x4090c834, level 2): Holding 0x409ae36c, level 3.
Expect deadlock!
fixme:ras:RasEnumConnectionsA
2017 Feb 15
2
samba-tool domain classicupgrade smb_krb5_context_init_basic failed (Invalid argument)
On 15/02/17 14:40, Tom Robinson via samba wrote:
> On 13/02/17 10:18, Andrew Bartlett via samba wrote:
>> On Mon, 2017-02-13 at 10:00 +1100, Tom Robinson via samba wrote:
>>> On 12/02/17 03:13, Rowland Penny via samba wrote:
>>>> On Fri, 10 Feb 2017 12:34:23 +1100
>>>> Tom Robinson via samba <samba at lists.samba.org> wrote:
>>>>
2006 Jan 05
2
Re: sigsegv in _mm_load_ups (linux/gcc 3.x)
That's definitely strange and I've never encountered that. Normally, the
only way for _mm_load_ups to generate a segfault is for the input to be
invalid memory, in which case the C version should crash too. I suspect
the compiler (or something else) may be hiding the real problem. Can you
get a debugger and see exactly what assembly statement is causing the
crash and what the operands are?