search for: segv

libswfdec/swfdec_as_object.c | 62 +++++++++++++++------- test/trace/Makefile.am | 9 +++ test/trace/addProperty-set-prototypes-5.swf |binary test/trace/addProperty-set-prototypes-5.swf.trace | 4 + test/trace/addProperty-set-prototypes-6.swf |binary test/trace/addProperty-set-prototypes-6.swf.trace | 5 +

...he second time, I added the -V flag, but that didn't give me anything useful. The system is currently running CentOS 5.3. Nothing on the system has changed recently (that I am aware of). The Aide database hasn't been updated in a few months. This is the error I am seeing: Caught SIGBUS/SEGV while mmapping. File was truncated while aide was running? Caught SIGBUS/SEGV. Exiting I tried Googling for it, but didn't find anything helpful. Any ideas? -- Bowie

...ouldn't boot (into any runlevel), nor could I chroot into the root partition using a rescue disk. Unfortunately I didn't grab a screenshot, however the error(s) when booting were: /pre-pivot/50selinux-loadpolicy.sh: 14 <other messages> init: readahead main process (425) killed by SEGV signal init: readahead-col lector main process (421) killed by SEGV signal init: rcS pre-start process (425) killed by SEGV signal init: Error while reading from descriptor: Bad file descriptor init: readahead-col lector post-stop process (424) killed by SEGV signal init: rcS post-stop process (427...

Under the right circumstances, xenconsoled will corrupt its internal list of domains causing a SEGV. This is usually characterized by a rapid number of creations/destructions. The attached patch fixes this. Regards, Anthony Liguori _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

I'm getting a SEGV on a FreeBSD 4.8-STABLE box. The client is Solaris 9/SPARC. Both boxes run 2.6.2. The command I'm running is: $ rsync -arHRv --numeric-ids --delete --exclude=/opt/dist/cdrom \ [paths] [server]:[path] If I whittle down what appears in [paths], then it works. $ gdb rsync rsync.core gdb>...

Hello: I have a Windows 2003 Server that is causing rpcclient to SEGV via the following command: $ rpcclient -U Administrator%foobar -c 'netshareenum 502' <server> ... type: 0x6269: SEC_DESC_OWNER_DEFAULTED SEC_DESC_DACL_DEFAULTED SEC_DESC_SACL_DEFAULTED SEC_DESC_DACL_TRUSTED SEC_DESC_SACL_AUTO_INHERIT_REQ SEC_DESC_SACL_PROTECTED SEC_DESC_RM_CONTROL_VA...

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi all, 4.2 and 4.1 suffers from SEGV during xl network-attach in libxl__device_nic_add. In 4.3-unstable it is fixed by: 5420f2650 libxl: Set vfb and vkb devid if not done so by the caller So either the patch need to be backported to 4.1 and 4.2, or fixed by this one: - ------ libxl: Fix SEGV in network-attach When "device/vif&q...

...tl -l status dovecot.service dovecot.service - Dovecot IMAP/POP3 email server Loaded: loaded (/usr/lib/systemd/system/dovecot.service; disabled) Active: failed (Result: core-dump) since Thu 2014-11-13 19:05:52 EST; 30min ago Process: 23700 ExecStart=/usr/sbin/dovecot -F (code=dumped, signal=SEGV) Process: 23695 ExecStartPre=/usr/libexec/dovecot/prestartscript (code=exited, status=0/SUCCESS) Main PID: 23700 (code=dumped, signal=SEGV) Nov 13 19:05:52 dungeon.the-leveys.us systemd[1]: Started Dovecot IMAP/POP3 email server. Nov 13 19:05:52 dungeon.the-leveys.us systemd[1]: dovecot.service...

Hello, I've been trying out the bleeding edge, 1.2.alpha4. I'm having a problem with deliver and dovecot-1.2-sieve-0.1.1. I get a segv on this sieve script: require ["fileinto", "reject", "vacation", "envelope", "regex"]; if header :contains "subject" ["urgent"] { redirect "someone at somewhere.net"; fileinto "test"; } Seems its happeni...

...fffffffff] LowShadow This is quite a lot, I can not mmap/mprotect this thing. So, I basically *hope* that it won't be used by anyone but the ASAN run time (of course, there are asserts here and there to check it). When some part of the shadow region is being written to (when we poison memory), SEGV happens and the SEGV handler mmaps the required region. > If I'm not mistaken, the Native Client > guys have done a memory place-holder, with enough space pre- and > post-code, is it similar of what you're doing? Not very similar. 64-bit NaCl mmaps 88G of address space. On 64-...

...; This is quite a lot, I can not mmap/mprotect this thing. > So, I basically *hope* that it won't be used by anyone but the ASAN run > time (of course, there are asserts here and there to check it). > When some part of the shadow region is being written to (when we poison > memory), SEGV happens and the SEGV handler mmaps the required region. > Ok, if you allocate big enough regions you shouldn't need to SEGV that often. -- cheers, --renato http://systemcall.org/ Reclaim your digital rights, eliminate DRM, learn more at http://www.defectivebydesign.org/what_is_drm ----...

On Tue, Sep 6, 2016 at 1:55 AM, Olivier <oza.4h07 at gmail.com> wrote: > Hello, > > After testing "pkill -SEGV -f /usr/sbin/asterisk" on Debian Jessie > platform, I've got several questions : > > > 1. When I issue a "cd /tmp; asterisk -cvvvvvvvvvvvg -U asterisk -G > asterisk" command, and then issue a "pkill -SEGV asterisk" command, > I can read on Asterisk co...

...bove are the kernel messages from two runs of xl. In this case the files were read-only due to a bug in SE Linux policy, but they could be read-only due to a filesystem error, use of chattr +i, or other reasons. It would be OK for xl to report an error and abort, pretty much anything other than a SEGV would do. -- System Information: Debian Release: 8.0 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) She...

...s id 4735) Password: rpcclient $> enumprinters flags:[0x800000] name:[\\xxxxxxx\hpem] description:[\\xxxxxxx\hpem,HP LaserJet 4050 Series PS,HP LaserJet 4050N PS] comment:[HP LaserJet 4050N PS] (trimmed) rpcclient $> getdriver hpem [Windows NT x86] signal SEGV (no mapping at the fault address) in strlen_w at 0x778d4 0x000778d4: strlen_w+0x0004: lduh [%o0], %g3 (dbx) where =>[1] strlen_w(0x0, 0x1caf00, 0x1f, 0xffbed760, 0x36, 0x0), at 0x778d4 [2] rpcstr_pull(0xffbecfe0, 0x0, 0x0, 0x0, 0x1, 0x100), at 0x797ac [3] display_print_driver_3(0x1,...

...chroot into the root partition using > a rescue disk. > > Unfortunately I didn't grab a screenshot, however the error(s) when > booting were: > > > /pre-pivot/50selinux-loadpolicy.sh: 14 > > <other messages> > > init: readahead main process (425) killed by SEGV signal > init: readahead-col lector main process (421) killed by SEGV signal > init: rcS pre-start process (425) killed by SEGV signal > init: Error while reading from descriptor: Bad file descriptor > init: readahead-col lector post-stop process (424) killed by SEGV signal > init: r...

Author: danmcd Repository: /hg/zfs-crypto/gate Revision: 2a6337da4889d9ac5903e22f957cb2c15d695d6b Log message: 6392589 ipsecalgs build with sgcc cores with SEGV Files: update: usr/src/lib/libipsecutil/common/algs.c

This is on FreeBSD 4.6-STABLE, doing an mget with wildcard char on a non-existent file(s) produces a SEGV. Reproduce the bug as follows (Note: "zqw*" is a pattern that does not match): % sftp user at host user at host's password: sftp> mget zqw* Program received signal SIGSEGV, Segmentation fault. 0x804c5db in process_get (conn=0x80520e0, src=0x80540b0 "zwq*", dst=0x0,...

Ok, folks, I brought this up some time ago, and got no replies. We have a good number of systems - > 100 - and we use sssd. On the C 7 boxen, which is most of them, gssproxy *frequently* (like once a day or so) dies with a SEGV. It restarts fine. Dies again eventually. ARE other people seeing this? If so, I guess we get to file a bug report with upstream. Speaking as an old C programmer, dying with a SEGV? Really? In production? mark

...gt;> >> 1. To my knowledge, no tool exists for this. Is it correct ? >> 2. If such tool do not exist, what would you say about something like >> "core stop panic", "core stop segfault" or whatever ? >> > > > How about just running "pkill -SEGV -f /usr/sbin/asterisk" from the shell? > It seems to comply to what I'm after. Thank you very for sharing this here. > Works for me. > > > >> >> Best Regards >> >> >> >> -- >> ____________________________________________________...

Hi, I'm trying to set-up a VPN using Tinc 1.0pre3. When I start tincd I get the following in /var/log/messages. On the machine that listens for incomming connections: > Mar 16 17:23:24 vpn tinc[1168]: tincd 1.0pre3 starting > Mar 16 17:23:24 vpn tinc[1168]: Ready: listening on port 655 On the machine making the connection: > Mar 16 17:16:51 mail tinc[802]: tincd 1.0pre3 starting