segmentation-fault

C++ libpthread program segfaults for unknown reason

吃可爱长大的小学妹 提交于 2019-12-11 06:18:32
问题 I have a libpthread linked application. The core of the application are two FIFOs shared by four threads ( two threads per one FIFO that is ;). The FIFO class is synchronized using pthread mutexes and it stores pointers to big classes ( containing buffers of about 4kb size ) allocated inside static memory using overloaded new and delete operators ( no dynamic allocation here ). The program itself usually works fine, but from time to time it segfaults for no visible reason. The problem is,

Segmentation fault when starting jvm using jpype

眉间皱痕 提交于 2019-12-11 05:35:49
问题 I am trying to use java sutime in my Python code. The code has been working fine until yesterday but now ends with Segmentation fault. The problem seems to be coming from jpype.startJVM(getDefaultJVMPath()) This function ends with Segmentation fault. The defaultJVMPath is '/usr/lib/jvm/java-8-oracle/jre/lib/amd64/server/libjvm.so' I have tried uninstalling and then installing java and jpype. The code works fine in virtual box with less memory, so the problem doesnt seems to be coming from

Converting 32-bit Fibonacci nasm code to 64-bit

帅比萌擦擦* 提交于 2019-12-11 05:13:41
问题 I'm a newbie in writing assembly code and I need some help. My task is to write a program in NASM (on Linux), which computes n-th Fibonacci number, where n is read from STDIN with read syscall and converted to int/long with C atoi/atol. The calculated number will be written to STDOUT (I can use C printf). I managed to write the working 32-bit code and I'm stuck at converting it to 64-bit (using 64-bit registers, 64-bit long int). I tried to do it naively (changing eax -> rax, esp -> rsp and

Blender: segmentation, fault core dumped?

故事扮演 提交于 2019-12-11 04:31:19
问题 Here is an add-on I'm trying to create: import bpy import os import sys import subprocess import time from threading import * class Repeat(Thread): def __init__(self,delay,function,*args,**kwargs): Thread.__init__(self) self.abort = Event() self.delay = delay self.args = args self.kwargs = kwargs self.function = function def stop(self): self.abort.set() def run(self): while not self.abort.isSet(): self.function(*self.args,**self.kwargs) self.abort.wait(self.delay) class ExportToGIMP(bpy.types

Using Python help throws SEGFAULT [closed]

我与影子孤独终老i 提交于 2019-12-11 04:02:16
问题 This question is unlikely to help any future visitors; it is only relevant to a small geographic area, a specific moment in time, or an extraordinarily narrow situation that is not generally applicable to the worldwide audience of the internet. For help making this question more broadly applicable, visit the help center. Closed 6 years ago . While using Python help I typed modules and got the following error: help> modules Please wait a moment while I gather a list of all available modules...

Symfony doctrine data-load segmentation fault

穿精又带淫゛_ 提交于 2019-12-11 03:57:07
问题 I'm working through the Symfony Jobeet tutorial and am getting a segmentation fault when trying to load data from my fixtures files. PHP 5.2.6-1+lenny8 with Suhosin-Patch 0.9.6.2 (cli), S symfony version 1.4.5 I'm using the Doctrine plugin. My fixtures below: /data/fixtures/categories.yml JobeetCategory: design: name: Design programming: name: Programming manager: name: Manager administrator: name: Administrator /data/fixtures/jobs.yml JobeetJob: job_sensio_labs: JobeetCategory: programming

Why might malloc'd memory from a shared library be inaccessible to the application?

时光总嘲笑我的痴心妄想 提交于 2019-12-11 03:50:56
问题 I maintain a library written in C, which is being accessed by a user on Linux, directly from Python using a module which loads the shared library and call functions. The module is very commonly used, as is this version of the shared library, by people doing a popular tutorial. The user is getting a segmentation fault. Running his Python script under gdb, he sees that it is in the shared library, within a function that mallocs memory for an struct and returns the pointer. He is getting a

Segmentation fault with Array in multiprocessing.sharedctypes

馋奶兔 提交于 2019-12-11 03:49:53
问题 I allocate a multiprocessing.sharedctypes.Array in order to be shared among processes. Wrapping this program is a generator that generate the result computed from that array. Before using the array for any parallel computation, I encounter Segmentation fault error after 2 iterations which I doubt caused by deallocation mechanism between C and Python. I can reproduce the error using the following simple code snippet: import numpy as np from multiprocessing import Pool, sharedctypes def

__memcpy_ssse3() segmentation fault

对着背影说爱祢 提交于 2019-12-11 03:48:16
问题 i'm working with Opencv, trying to copy some frame that captured from web camera. when copying the frame, i'm getting segmentation fault in __memcpy_ssse3() , line 160 or 1675. gdb shows: 0 __memmove_ssse3 () at ../sysdeps/i386/i686/multiarch/memcpy-ssse3.S:1675 1 0xb75ec6d0 in cv::Mat::copyTo (this=0xbfca3450, _dst=...) at /home/david/opencv/OpenCV-2.4.2/modules/core/src/copy.cpp:181 2 0xb75984f6 in cv::Mat::Mat (this=0xbfca358c, img=0xb1300c90, copyData=true) at /home/david/opencv/OpenCV-2

pthread_exit in signal handler causes segmentation fault

我与影子孤独终老i 提交于 2019-12-11 03:34:44
问题 The program below sets SIG_ALRM handler for the whole process, creates a thread, sends SIG_ALRM signal to new created thread. In SIG_ALRM handler pthread_exit is called. The result - segmentation fault. If you sleep before sending signal - OK. It looks like new thread has not been started at the moment of pthread_exit. I tried to locate segmentation fault with gdb but couldn't reproduce the crash with gdb. What causes segmentation fault? Thanks! #include <signal.h> #include <pthread.h>