So I believe this is just a problem on unix and that it occurs at the first fscanf if the Clion debugger was right, but I don’t know why I get the error- Process finished with exit code 139 (interrupted by signal 11: SIGSEGV) — why?
struct loginInformation
{
char username[USERNAME_LENGTH];
char password[PASSWORD_LENGTH];
int type;
}accounts[NUM_OF_ACCOUNTS];
void createAccountsFromFile()
{
FILE *input = fopen("accounts.txt", "r");
int counter;
for(counter = 0; counter < NUM_OF_ACCOUNTS; counter++)
{
fscanf(input, "%s", accounts[counter].username);
fscanf(input, "%s", accounts[counter].password);
fscanf(input, "%d", &accounts[counter].type);
}
}
int main()
{
createAccountsFromFile();
}
accounts.txt
user1
pass1
0
user2
pass2
1
user3
pass3
2
user4
pass4
3
asked Mar 19, 2017 at 2:13
michael leemichael lee
3312 gold badges3 silver badges9 bronze badges
7
It means the program crashed before it exited. You need to debug the program. For example, you need to check whether the file is successfully opened after fopen.
answered Mar 19, 2017 at 2:14
xuhdevxuhdev
7,6302 gold badges40 silver badges64 bronze badges
1
SIGSEGV are not always thrown due to a root cause of memory access problems…
Perl throws a 139 on Unix usually because of file I/O. You might have accidentally deleted your input files.
user7610
23.5k12 gold badges115 silver badges139 bronze badges
answered Nov 22, 2017 at 16:00
BAMF4baconBAMF4bacon
4941 gold badge6 silver badges19 bronze badges
TL;DR: Your program tried to access a memory location it had no permissions to access, so the operating system killed it.
First: The code «139» doesn’t matter, forget about the number. Your program was terminated after «getting a SIGSEGV», or a signall regarding a segmentation violation. Read about what that means here:
What causes a SIGSEGV
(never mind that question is about C++, same idea.)
Now, why would this happen? You must be making some assumptions you shouldn’t be. Looking at your code, it might be:
- Reading a very long string from the file which exceeds the bounds of the
loginInformationarray — and perhaps even the bounds of the memory region allocated to your program overall. - Scanning from an invalid-state/uninitialized/null file descriptor, as in @xuhdev’s answer
- (Unlikely/impossible) Ignoring some error generated by one of the
fscanf()calls (you need to checkerrnoif a scan failed).
I think that covers it although maybe I missed something. Instead of speculating you can actually check what happened using a debugger on the core dump:
How do I analyze a program’s core dump file with GDB when it has command-line parameters?
answered Mar 19, 2017 at 18:48
einpoklumeinpoklum
112k53 gold badges311 silver badges630 bronze badges
3
On Perl programmation RC 139 caused by «Out of memory» for me.
Because there have been too much data in a variable (millions).
I have done a segmentation manualy by release (undef) this variable regularly.
This solved this.
answered Sep 23, 2022 at 14:08
1
What is SIGSEGV
SIGSEGV, also known as a segmentation violation or segmentation fault, is a signal used by Unix-based operating systems (such as Linux). It indicates an attempt by a program to write or read outside its allocated memory—either because of a programming error, a software or hardware compatibility issue, or a malicious attack, such as buffer overflow.
SIGSEGV is indicated by the following codes:
- In Unix/Linux, SIGSEGV is operating system signal 11
- In Docker containers, when a Docker container terminates due to a SIGSEV error, it throws exit code 139
The default action for SIGSEGV is abnormal termination of the process. In addition, the following may take place:
- A core file is typically generated to enable debugging
- SIGSEGV signals may logged in more detail for troubleshooting and security purposes
- The operating system may perform platform-specific operations
- The operating system may allow the process itself to handle the segmentation violation
SIGSEGV is a common cause for container termination in Kubernetes. However, Kubernetes does not trigger SIGSEGV directly. To resolve the issue, you will need to debug the problematic container or the underlying host.
SIGSEGV (exit code 139) vs SIGABRT (exit code 134)
SIGSEGV and SIGABRT are two Unix signals that can cause a process to terminate.
SIGSEGV is triggered by the operating system, which detects that a process is carrying out a memory violation, and may terminate it as a result.
SIGABRT (signal abort) is a signal triggered by a process itself. It abnormally terminates the process, closes and flushes open streams. Once it is triggered, it cannot be blocked by the process (similar to SIGKILL, but different in that SIGKILL is triggered by the operating system).
Before the SIGABRT signal is sent, the process may:
- Call the
abort()function in thelibclibrary, which unlocks the SIGABRT signal. Then the process can abort itself by triggering SIGABRT - Call the
assert()macro, which is used in debugging, and aborts the program using SIGABRT if the assertion is false.
Exit codes 139 and 134 are parallel to SIGSEGV and SIGABRT in Docker containers:
- Docker exit code 139—means the container received a SIGSEGV by the underlying operating system due to a memory violation
- Docker exit code 134—means the container triggered a SIGABRT and was abnormally terminated
What Causes SIGSEGV?
Modern general-purpose computing systems include memory management units (MMUs). An MMU enables memory protection in operating systems like Linux—preventing different processes from accessing or modifying each other’s memory, except via a strictly controlled API. This simplifies troubleshooting and makes processes more resilient, because they are carefully isolated from each other.
A SIGSEGV signal or segmentation error occurs when a process attempts to use a memory address that was not assigned to it by the MMU. This can happen for three common reasons:
- Coding error—segmentation violations can occur if a process is not initialized properly, or if it tries to access memory through a pointer to previously freed memory. This will result in a segmentation violation in a specific process or binary file under specific circumstances.
- Incompatibility between binaries and libraries—if a process runs a binary file that is not compatible with a shared library, it can result in segmentation violations. For example, if a developer updates a library, changing its binary interface, but does not update the version number, an older binary may be loaded against the newer version. This may result in the older binary trying to access inappropriate memory addresses.
- Hardware incompatibility or misconfiguration—if segmentation violations occur frequently across multiple libraries, with no repeating pattern, this may indicate a problem with the memory subsystems on the machine or improper low-level system configuration settings.
Handling SIGSEGV Errors
On a Unix-based operating system, by default, a SIGSEGV signal will result in abnormal termination of the violating process.
Additional actions performed by the operating system
In addition to terminating the process, the operating system may generate core files to assist with debugging, and can also perform other platform-dependent operations. For
example, on Linux, you can use the grsecurity utility to log SIGSEGV signals in detail, to monitor for related security risks such as buffer overflow.
Allowing the process to handle SIGSEGV
On Linux and Windows, the operating system allows processes to handle their response to segmentation violations. For example, the program can collect a stack trace with information like processor register values and the memory addresses that were involved in the segmentation fault.
An example of this is segvcatch, a C++ library that supports multiple operating systems, and is able to convert segmentation faults and other hardware related exceptions to software language exceptions. This makes it possible to handle “hard” errors like segmentation violations with simple try/catch code. This makes it possible for software to identify a segmentation violation and correct it during program execution.
Troubleshooting SIGSEGV
When troubleshooting segmentation errors, or testing programs to avoid these errors, there may be a need to intentionally cause a segmentation violation to investigate its impact. Most operating systems make it possible to handle SIGSEGV in such a way that they will allow the program to run even after the segmentation error occurs, to allow for investigation and logging.
Troubleshooting Common Segmentation Faults in Kubernetes
SIGSEGV faults are highly relevant for Kubernetes users and administrators. It is fairly common for a container to fail due to a segmentation violation.
However, unlike other signals such as SIGTERM and SIGKILL, Kubernetes does not trigger a SIGSEGV signal directly. Rather, the host machine on a Kubernetes node can trigger SIGSEGV when a container is caught performing a memory violation. The container then terminates, Kubernetes detects this, and may attempt to restart it depending on the pod configuration.
When a Docker container is terminated by a SIGSEGV signal, it throws exit code 139. This can indicate:
- An issue with application code in one of the libraries running on the container
- An incompatibility between different libraries running on the container
- An incompatibility between those libraries and hardware on the host
- Issues with the host’s memory management systems or a memory misconfiguration
To debug and resolve a SIGSEGV issue on a container, follow these steps:
- Get root access to the host machine, and review the logs to see additional information about the buggy container. A SIGSEGV error looks like the following in kubelet logs:
[signal SIGSEGV: segmentation violation code=0x1 addr=0x18 pc=0x1bdaed0]
- Try to identify in which layer of the container image the error occurs—it could be in your specific application code, or lower down in the base image of the container.
- Run
docker pull [image-id]to pull the image for the container terminated by SIGSEGV. - Make sure that you have debugging tools (e.g. curl or vim) installed, or add them.
- Use
kubectlto execute into the container. See if you can replicate the SIGSEGV error to confirm which library is causing the issue. - If you have identified the library or libraries causing the memory violation, try to modify your image to fix the library causing the memory violation, or replace it with another library. Very often, updating a library to a newer version, or a version that is compatible with the environment on the host, will resolve the issue.
- If you cannot identify a library that is consistently causing the error, the problem may be on the host. Check for problems with the host’s memory configuration or memory hardware.
The process above can help you resolve straightforward SIGSEGV errors, but in many cases troubleshooting can become very complex and require non-linear investigation involving multiple components. That’s exactly why we built Komodor – to troubleshoot memory errors and other complex Kubernetes issues before they get out of hand.
Troubleshooting Kubernetes Container Termination with Komodor
As a Kubernetes administrator or user, pods or containers terminating unexpectedly can be a pain, and can result in severe production issues. Container termination can be a result of multiple issues in different components and can be difficult to diagnose. The troubleshooting process in Kubernetes is complex and, without the right tools, can be stressful, ineffective and time-consuming.
Some best practices can help minimize the chances of SIGSEGV or SIGABRT signals affecting your applications, but eventually something will go wrong—simply because it can.
This is the reason why we created Komodor, a tool that helps dev and ops teams stop wasting their precious time looking for needles in (hay)stacks every time things go wrong.
Acting as a single source of truth (SSOT) for all of your k8s troubleshooting needs, Komodor offers:
- Change intelligence: Every issue is a result of a change. Within seconds we can help you understand exactly who did what and when.
- In-depth visibility: A complete activity timeline, showing all code and config changes, deployments, alerts, code diffs, pod logs and etc. All within one pane of glass with easy drill-down options.
- Insights into service dependencies: An easy way to understand cross-service changes and visualize their ripple effects across your entire system.
- Seamless notifications: Direct integration with your existing communication channels (e.g., Slack) so you’ll have all the information you need, when you need it.
If you are interested in checking out Komodor, use this link to sign up for a Free Trial.
Running the problem with new python version gives more insights for the error. Does some one can interpret?
Process: Python [3675]
Path: /Library/Frameworks/Python.framework/Versions/3.8/Resources/Python.app/Contents/MacOS/Python
Identifier: Python
Version: 3.8.2 (3.8.2)
Code Type: X86-64 (Native)
Parent Process: pycharm [282]
Responsible: Python [3675]
User ID: 502
Date/Time: 2020-05-06 23:34:02.776 +0200
OS Version: Mac OS X 10.14.6 (18G95)
Report Version: 12
Bridge OS Version: 4.2 (17P2551)
Anonymous UUID: AD5048B0-3919-172C-029F-B06F480E75FA
Sleep/Wake UUID: AEB6CF63-BB92-4CE2-910C-69077D30D00A
Time Awake Since Boot: 25000 seconds
Time Since Wake: 7700 seconds
System Integrity Protection: enabled
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x00007fba8f9fb7f8
Exception Note: EXC_CORPSE_NOTIFY
Termination Signal: Segmentation fault: 11
Termination Reason: Namespace SIGNAL, Code 0xb
Terminating Process: exc handler [3675]
VM Regions Near 0x7fba8f9fb7f8:
MALLOC_TINY 00007fb695900000-00007fb695a00000 [ 1024K] rw-/rwx SM=PRV
-->
STACK GUARD 00007ffee2f15000-00007ffee2f16000 [ 4K] ---/rwx SM=NUL stack guard for thread 0
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 cbc-c-darwin-x86-64.dylib 0x000000011b68a181 Idiot::crossOver(int) + 4545
1 cbc-c-darwin-x86-64.dylib 0x000000011b683958 Idiot::crash(int, CoinMessageHandler*, CoinMessages const*, bool) + 568
2 cbc-c-darwin-x86-64.dylib 0x000000011b66d7b8 ClpSimplex::initialSolve(ClpSolve&) + 33544
3 cbc-c-darwin-x86-64.dylib 0x000000011b517e62 OsiClpSolverInterface::initialSolve() + 1458
4 cbc-c-darwin-x86-64.dylib 0x000000011b2dbf22 Cbc_solveLinearProgram + 2306
5 cbc-c-darwin-x86-64.dylib 0x000000011b2dc12c Cbc_solve + 124
6 libffi.dylib 0x00007fff7a6cbf6c ffi_call_unix64 + 76
7 libffi.dylib 0x00007fff7a6cc775 ffi_call + 785
8 _cffi_backend.cpython-38-darwin.so 0x00000001132a8359 cdata_call + 905
9 org.python.python 0x000000010bd17785 _PyObject_MakeTpCall + 373
10 org.python.python 0x000000010bde5ed5 call_function + 533
11 org.python.python 0x000000010bde2c8d _PyEval_EvalFrameDefault + 25677
12 org.python.python 0x000000010bde6cc4 _PyEval_EvalCodeWithName + 2804
13 org.python.python 0x000000010bd1826e _PyFunction_Vectorcall + 270
14 org.python.python 0x000000010bde5e7c call_function + 444
15 org.python.python 0x000000010bde2c69 _PyEval_EvalFrameDefault + 25641
16 org.python.python 0x000000010bde6cc4 _PyEval_EvalCodeWithName + 2804
17 org.python.python 0x000000010bd1826e _PyFunction_Vectorcall + 270
18 org.python.python 0x000000010bd1a79a method_vectorcall + 170
19 org.python.python 0x000000010bde5e7c call_function + 444
20 org.python.python 0x000000010bde2db4 _PyEval_EvalFrameDefault + 25972
21 org.python.python 0x000000010bde6cc4 _PyEval_EvalCodeWithName + 2804
22 org.python.python 0x000000010bd1826e _PyFunction_Vectorcall + 270
23 org.python.python 0x000000010bde5e7c call_function + 444
24 org.python.python 0x000000010bde2d1a _PyEval_EvalFrameDefault + 25818
25 org.python.python 0x000000010bde6cc4 _PyEval_EvalCodeWithName + 2804
26 org.python.python 0x000000010bd1826e _PyFunction_Vectorcall + 270
27 org.python.python 0x000000010bde5e7c call_function + 444
28 org.python.python 0x000000010bde2d1a _PyEval_EvalFrameDefault + 25818
29 org.python.python 0x000000010bde6cc4 _PyEval_EvalCodeWithName + 2804
30 org.python.python 0x000000010bd1826e _PyFunction_Vectorcall + 270
31 org.python.python 0x000000010bde5e7c call_function + 444
32 org.python.python 0x000000010bde2d1a _PyEval_EvalFrameDefault + 25818
33 org.python.python 0x000000010bde6cc4 _PyEval_EvalCodeWithName + 2804
34 org.python.python 0x000000010bd1826e _PyFunction_Vectorcall + 270
35 org.python.python 0x000000010bde5e7c call_function + 444
36 org.python.python 0x000000010bde2db4 _PyEval_EvalFrameDefault + 25972
37 org.python.python 0x000000010bde6cc4 _PyEval_EvalCodeWithName + 2804
38 org.python.python 0x000000010bddc764 PyEval_EvalCode + 100
39 org.python.python 0x000000010be2c370 PyRun_FileExFlags + 336
40 org.python.python 0x000000010be2ba60 PyRun_SimpleFileExFlags + 864
41 org.python.python 0x000000010be48cdf Py_RunMain + 2159
42 org.python.python 0x000000010be4901f pymain_main + 223
43 org.python.python 0x000000010be4921b Py_BytesMain + 43
44 libdyld.dylib 0x00007fff7cb223d5 start + 1
Thread 1:
0 libsystem_kernel.dylib 0x00007fff7cc5a86a __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff7cd1956e _pthread_cond_wait + 722
2 libopenblasp-r0.3.7.dylib 0x000000010cd3dc3b blas_thread_server + 619
3 libsystem_pthread.dylib 0x00007fff7cd162eb _pthread_body + 126
4 libsystem_pthread.dylib 0x00007fff7cd19249 _pthread_start + 66
5 libsystem_pthread.dylib 0x00007fff7cd1540d thread_start + 13
Thread 2:
0 libsystem_kernel.dylib 0x00007fff7cc5a86a __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff7cd1956e _pthread_cond_wait + 722
2 libopenblasp-r0.3.7.dylib 0x000000010cd3dc3b blas_thread_server + 619
3 libsystem_pthread.dylib 0x00007fff7cd162eb _pthread_body + 126
4 libsystem_pthread.dylib 0x00007fff7cd19249 _pthread_start + 66
5 libsystem_pthread.dylib 0x00007fff7cd1540d thread_start + 13
Thread 3:
0 libsystem_kernel.dylib 0x00007fff7cc5a86a __psynch_cvwait + 10
1 libsystem_pthread.dylib 0x00007fff7cd1956e _pthread_cond_wait + 722
2 libopenblasp-r0.3.7.dylib 0x000000010cd3dc3b blas_thread_server + 619
3 libsystem_pthread.dylib 0x00007fff7cd162eb _pthread_body + 126
4 libsystem_pthread.dylib 0x00007fff7cd19249 _pthread_start + 66
5 libsystem_pthread.dylib 0x00007fff7cd1540d thread_start + 13
Thread 4:
0 libsystem_pthread.dylib 0x00007fff7cd153f0 start_wqthread + 0
Thread 5:
0 libsystem_pthread.dylib 0x00007fff7cd153f0 start_wqthread + 0
Thread 0 crashed with X86 Thread State (64-bit):
rax: 0x0000000000000033 rbx: 0x0000000000000050 rcx: 0x0000000000000033 rdx: 0x0000000000000000
rdi: 0x00007fb6901fb800 rsi: 0x000000007fefffff rbp: 0x00007ffee3f12470 rsp: 0x00007ffee3f11cd0
r8: 0x00007fb695221660 r9: 0x00007fb695222aa0 r10: 0x00007fb69521fea0 r11: 0x00007fb6952203f0
r12: 0x00007fb695220010 r13: 0x00007fb6952214a8 r14: 0x000000000000002d r15: 0x00007fb69521fb20
rip: 0x000000011b68a181 rfl: 0x0000000000010246 cr2: 0x00007fba8f9fb7f8
Logical CPU: 2
Error Code: 0x00000004
Trap Number: 14
Binary Images:
0x10bcea000 - 0x10bceafff +org.python.python (3.8.2 - 3.8.2) <4A52E177-60C3-3B60-A1C5-3651F5857993> /Library/Frameworks/Python.framework/Versions/3.8/Resources/Python.app/Contents/MacOS/Python
0x10bcf7000 - 0x10bf2cfff +org.python.python (3.8.2, [c] 2001-2019 Python Software Foundation. - 3.8.2) <D386999B-3D21-310C-8015-1D3910C0D271> /Library/Frameworks/Python.framework/Versions/3.8/Python
0x10c331000 - 0x10c333ff7 +_heapq.cpython-38-darwin.so (0) <97A0811A-F821-3A44-BA9E-39269C2A058D> /Library/Frameworks/Python.framework/Versions/3.8/lib/python3.8/lib-dynload/_heapq.cpython-38-darwin.so
0x10c595000 - 0x10c8f3fe7 +_multiarray_umath.cpython-38-darwin.so (0) <4D269D8B-E945-3FAB-9B27-071C6EDD79D1> /Users/USER/Documents/*/_multiarray_umath.cpython-38-darwin.so
0x10ca07000 - 0x110472ae7 +libopenblasp-r0.3.7.dylib (0) <9914A383-F8C9-3559-BC88-B4DD28689BC5> /Users/USER/Documents/*/libopenblasp-r0.3.7.dylib
0x1106b2000 - 0x1107c9ff7 +libgfortran.3.dylib (0) <9ABE5EDE-AD43-391A-9E54-866711FAC32A> /Users/USER/Documents/*/libgfortran.3.dylib
0x11082d000 - 0x110863fff +libquadmath.0.dylib (0) <7FFA409F-FB04-3B64-BE9A-3E3A494C975E> /Users/USER/Documents/*/libquadmath.0.dylib
0x110872000 - 0x110887ff7 +libgcc_s.1.dylib (0) <7C6D7CB7-82DB-3290-8181-07646FEA1F80> /Users/USER/Documents/*/libgcc_s.1.dylib
0x112892000 - 0x11289afff +math.cpython-38-darwin.so (0) <B9C6CCC8-3E89-3BE8-8E95-D738725800AA> /Library/Frameworks/Python.framework/Versions/3.8/lib/python3.8/lib-dynload/math.cpython-38-darwin.so
0x1128a6000 - 0x1128b5ff7 +_datetime.cpython-38-darwin.so (0) <7BCE75EC-CBB5-3812-BD76-A3E3D0C73029> /Library/Frameworks/Python.framework/Versions/3.8/lib/python3.8/lib-dynload/_datetime.cpython-38-darwin.so
0x112906000 - 0x11290bff7 +_struct.cpython-38-darwin.so (0) <F49E476C-02AD-34C5-82B0-8E36C2346C50> /Library/Frameworks/Python.framework/Versions/3.8/lib/python3.8/lib-dynload/_struct.cpython-38-darwin.so
0x112918000 - 0x11292efff +_pickle.cpython-38-darwin.so (0) <8370183F-9899-3CE6-87A5-79BB58E6C07E> /Library/Frameworks/Python.framework/Versions/3.8/lib/python3.8/lib-dynload/_pickle.cpython-38-darwin.so
0x112a69000 - 0x112a76ff7 +_multiarray_tests.cpython-38-darwin.so (0) <ACCA8133-D875-3786-9491-E3E8F50AE677> /Users/USER/Documents/*/_multiarray_tests.cpython-38-darwin.so
0x112a87000 - 0x112a98ff7 +_ctypes.cpython-38-darwin.so (0) <B17DAED2-6EAE-33DE-A287-F17013E7FBA9> /Library/Frameworks/Python.framework/Versions/3.8/lib/python3.8/lib-dynload/_ctypes.cpython-38-darwin.so
0x112b2f000 - 0x112b30fff +lapack_lite.cpython-38-darwin.so (0) <321E5F11-D3E6-380B-8CEE-2E6806AE89CA> /Users/USER/Documents/*/lapack_lite.cpython-38-darwin.so
0x112b34000 - 0x112b4dffb +_umath_linalg.cpython-38-darwin.so (0) <1F7A4336-6B80-3409-ADCE-C7DBD8D5477D> /Users/USER/Documents/*/_umath_linalg.cpython-38-darwin.so
0x112c1c000 - 0x112c21ff7 +zlib.cpython-38-darwin.so (0) <34F60B9D-FC23-3864-A516-311A941DA8E9> /Library/Frameworks/Python.framework/Versions/3.8/lib/python3.8/lib-dynload/zlib.cpython-38-darwin.so
0x112c2b000 - 0x112c2dff7 +_bz2.cpython-38-darwin.so (0) <6D7B2A06-E971-37D4-BEB6-110865EBDAD8> /Library/Frameworks/Python.framework/Versions/3.8/lib/python3.8/lib-dynload/_bz2.cpython-38-darwin.so
0x112c36000 - 0x112c67fff +_lzma.cpython-38-darwin.so (0) <008EB489-2F28-3ED5-AC50-CBB9BDA5C363> /Library/Frameworks/Python.framework/Versions/3.8/lib/python3.8/lib-dynload/_lzma.cpython-38-darwin.so
0x112c75000 - 0x112c76ff7 +grp.cpython-38-darwin.so (0) <D4BC9BD3-C6C8-37FD-8165-A54FDD0E01A4> /Library/Frameworks/Python.framework/Versions/3.8/lib/python3.8/lib-dynload/grp.cpython-38-darwin.so
0x112c7e000 - 0x112cc7fff +_decimal.cpython-38-darwin.so (0) <1E040E50-F879-3180-B9FC-3940CE5FF157> /Library/Frameworks/Python.framework/Versions/3.8/lib/python3.8/lib-dynload/_decimal.cpython-38-darwin.so
0x112d26000 - 0x112d37ffb +_pocketfft_internal.cpython-38-darwin.so (0) <F3F11219-6ACF-3689-A48E-969559212D9A> /Users/USER/Documents/*/_pocketfft_internal.cpython-38-darwin.so
0x112d7b000 - 0x112de6fff +mtrand.cpython-38-darwin.so (0) <88DF27A0-E3C4-3E17-898F-607E9DCC4B70> /Users/USER/Documents/*/mtrand.cpython-38-darwin.so
0x112e3a000 - 0x112e58fff +_bit_generator.cpython-38-darwin.so (0) <5B6C2120-BA69-3EEA-B731-6840DC2E8CDF> /Users/USER/Documents/*/_bit_generator.cpython-38-darwin.so
0x112e73000 - 0x112ea3ff3 +_common.cpython-38-darwin.so (0) <420B4D81-5725-30D4-A9F3-4A678753DDEB> /Users/USER/Documents/*/_common.cpython-38-darwin.so
0x112ef8000 - 0x112efcfff +binascii.cpython-38-darwin.so (0) <80448651-FE0F-311A-8CF3-FBDEF71399E4> /Library/Frameworks/Python.framework/Versions/3.8/lib/python3.8/lib-dynload/binascii.cpython-38-darwin.so
0x112f05000 - 0x112f08ff7 +_hashlib.cpython-38-darwin.so (0) <38EE8FA7-0D62-3779-950C-B912CEA099FE> /Library/Frameworks/Python.framework/Versions/3.8/lib/python3.8/lib-dynload/_hashlib.cpython-38-darwin.so
0x112f12000 - 0x112f6aff7 +libssl.1.1.dylib (0) <03EE0DE4-2AA6-3672-B3DE-1FA1503B744B> /Library/Frameworks/Python.framework/Versions/3.8/lib/libssl.1.1.dylib
0x112f99000 - 0x1131ab1af +libcrypto.1.1.dylib (0) <7BFB4DF7-C953-36DF-9C59-1AD445C96D65> /Library/Frameworks/Python.framework/Versions/3.8/lib/libcrypto.1.1.dylib
0x113266000 - 0x113273fff +_socket.cpython-38-darwin.so (0) <716E93B0-2AA3-31CA-945F-B9E94916928D> /Library/Frameworks/Python.framework/Versions/3.8/lib/python3.8/lib-dynload/_socket.cpython-38-darwin.so
0x113280000 - 0x113287ff7 +array.cpython-38-darwin.so (0) <8E870952-E12D-3768-B917-F20C337D8327> /Library/Frameworks/Python.framework/Versions/3.8/lib/python3.8/lib-dynload/array.cpython-38-darwin.so
0x113294000 - 0x1132b2ffb +_cffi_backend.cpython-38-darwin.so (0) <4652037D-440F-385E-90E7-2B88EB0FEB0C> /Users/USER/Documents/*/_cffi_backend.cpython-38-darwin.so
0x1132da000 - 0x1132e0fff +_blake2.cpython-38-darwin.so (0) <42F3F8C5-B97B-35E6-BE65-BA553E2BF1E0> /Library/Frameworks/Python.framework/Versions/3.8/lib/python3.8/lib-dynload/_blake2.cpython-38-darwin.so
0x1132ea000 - 0x1132fafff +_sha3.cpython-38-darwin.so (0) <5FC33242-7487-3497-80CB-2A722EAC0294> /Library/Frameworks/Python.framework/Versions/3.8/lib/python3.8/lib-dynload/_sha3.cpython-38-darwin.so
0x113304000 - 0x113305ff7 +_bisect.cpython-38-darwin.so (0) <32F2A2ED-4C32-3C76-A818-3FF0632C680D> /Library/Frameworks/Python.framework/Versions/3.8/lib/python3.8/lib-dynload/_bisect.cpython-38-darwin.so
0x11330d000 - 0x113311ff7 +_sha512.cpython-38-darwin.so (0) <1A72D84C-27FB-3C21-AA1F-1F9759AEA518> /Library/Frameworks/Python.framework/Versions/3.8/lib/python3.8/lib-dynload/_sha512.cpython-38-darwin.so
0x113319000 - 0x11331aff7 +_random.cpython-38-darwin.so (0) <3D63FC3A-D70D-3270-8CB8-E935544587D2> /Library/Frameworks/Python.framework/Versions/3.8/lib/python3.8/lib-dynload/_random.cpython-38-darwin.so
0x113323000 - 0x113374ffb +_bounded_integers.cpython-38-darwin.so (0) <7584BD90-692E-3D61-AD4B-2D3F8A845DC4> /Users/USER/Documents/*/_bounded_integers.cpython-38-darwin.so
0x113397000 - 0x1133aaff3 +_mt19937.cpython-38-darwin.so (0) <CEAF9A43-E413-3369-9CC3-CFCCBB006776> /Users/USER/Documents/*/_mt19937.cpython-38-darwin.so
0x1133b6000 - 0x1133c3ff7 +_philox.cpython-38-darwin.so (0) <D163D6DC-0FB5-3492-ACC1-570AA0F7BB1A> /Users/USER/Documents/*/_philox.cpython-38-darwin.so
0x1133ce000 - 0x1133d8ffb +_pcg64.cpython-38-darwin.so (0) <E5033958-3FE4-39A1-A9C9-A729B40913E8> /Users/USER/Documents/*/_pcg64.cpython-38-darwin.so
0x1133e3000 - 0x1133ebffb +_sfc64.cpython-38-darwin.so (0) <B60D4DF0-461B-3D71-A347-03B093FA3267> /Users/USER/Documents/*/_sfc64.cpython-38-darwin.so
0x1133f5000 - 0x113477ff7 +_generator.cpython-38-darwin.so (0) <E3F40690-8025-3E8D-A37B-FD26A6F1EC71> /Users/USER/Documents/*/_generator.cpython-38-darwin.so
0x113550000 - 0x113584ffb +conversion.cpython-38-darwin.so (0) <C71D62AB-3C34-33EC-8154-2F6D9A2C42FA> /Users/USER/Documents/*/conversion.cpython-38-darwin.so
0x1135a2000 - 0x1135ccff7 +c_timestamp.cpython-38-darwin.so (0) <2ADE95F8-1EF3-3E9E-8F66-1BEF8076ACDB> /Users/USER/Documents/*/c_timestamp.cpython-38-darwin.so
0x1135e9000 - 0x11360dff7 +nattype.cpython-38-darwin.so (0) <F5AF0F80-804F-3357-B82A-98A45C993125> /Users/USER/Documents/*/nattype.cpython-38-darwin.so
0x11362e000 - 0x113650fff +missing.cpython-38-darwin.so (0) <8169A8F4-E00E-3A93-AF97-7EDE3E099F50> /Users/USER/Documents/*/missing.cpython-38-darwin.so
0x11366e000 - 0x113676fff +np_datetime.cpython-38-darwin.so (0) <1F0FFFDD-EF18-39C0-8E7F-54F07F3C128D> /Users/USER/Documents/*/np_datetime.cpython-38-darwin.so
0x11367e000 - 0x113684ffb +ops_dispatch.cpython-38-darwin.so (0) <E19E5846-EB62-3147-B8AC-871548FC10C9> /Users/USER/Documents/*/ops_dispatch.cpython-38-darwin.so
0x11368e000 - 0x1136b5ffb +timezones.cpython-38-darwin.so (0) <48D717E5-B9A6-3CDD-A002-4181907BC635> /Users/USER/Documents/*/timezones.cpython-38-darwin.so
0x113710000 - 0x113748ff7 +tzconversion.cpython-38-darwin.so (0) <742DB63C-BA41-3366-8E4F-46FA52F6DD9A> /Users/USER/Documents/*/tzconversion.cpython-38-darwin.so
0x113767000 - 0x1137baffb +timedeltas.cpython-38-darwin.so (0) <96BC20F5-20A3-3DE4-8588-EA8C754518E1> /Users/USER/Documents/*/timedeltas.cpython-38-darwin.so
0x11382f000 - 0x113876ff3 +offsets.cpython-38-darwin.so (0) <08FB126B-0871-3BE1-AF19-AFD563E6CA43> /Users/USER/Documents/*/offsets.cpython-38-darwin.so
0x1138a7000 - 0x1138b0ffb +ccalendar.cpython-38-darwin.so (0) <2672C08A-4384-3BE4-B73E-3B8682553810> /Users/USER/Documents/*/ccalendar.cpython-38-darwin.so
0x1138fc000 - 0x1138fdfff +_posixsubprocess.cpython-38-darwin.so (0) <EF777AF5-5C5D-33FB-B6EE-1590AAD9D25D> /Library/Frameworks/Python.framework/Versions/3.8/lib/python3.8/lib-dynload/_posixsubprocess.cpython-38-darwin.so
0x113905000 - 0x113908ff7 +select.cpython-38-darwin.so (0) <AD6F2B1F-A1AB-3E4F-A641-94B7059ABEA0> /Library/Frameworks/Python.framework/Versions/3.8/lib/python3.8/lib-dynload/select.cpython-38-darwin.so
0x113912000 - 0x11395affb +strptime.cpython-38-darwin.so (0) <E2AAF2BF-AFC5-33DB-9F81-2CDA26303495> /Users/USER/Documents/*/strptime.cpython-38-darwin.so
0x1139c8000 - 0x1139f2ff7 +fields.cpython-38-darwin.so (0) <DB382A4E-36DD-3BAD-A443-BD3AB5A33667> /Users/USER/Documents/*/fields.cpython-38-darwin.so
0x113a0e000 - 0x113a59ffb +parsing.cpython-38-darwin.so (0) <C485477F-25CE-391B-ADC7-C1135FF6991E> /Users/USER/Documents/*/parsing.cpython-38-darwin.so
0x113a88000 - 0x113a9dffb +frequencies.cpython-38-darwin.so (0) <2DEC1AE5-4660-3340-BA0E-DC43AB1EEA86> /Users/USER/Documents/*/frequencies.cpython-38-darwin.so
0x113af0000 - 0x113b3ffff +period.cpython-38-darwin.so (0) <1FDF42A9-4913-3CC3-8F48-1F7AFC862915> /Users/USER/Documents/*/period.cpython-38-darwin.so
0x113b6f000 - 0x113ba3ff3 +timestamps.cpython-38-darwin.so (0) <4AB0110C-FF4C-3FF0-9FB5-81E91E99FC54> /Users/USER/Documents/*/timestamps.cpython-38-darwin.so
0x113bcf000 - 0x113bf8fff +resolution.cpython-38-darwin.so (0) <E6CD6073-7315-37EF-B644-5B5EEC3E0593> /Users/USER/Documents/*/resolution.cpython-38-darwin.so
0x113c17000 - 0x113c8bfff +hashtable.cpython-38-darwin.so (0) <3E398FA7-9E31-363B-8753-834EF5D79C5F> /Users/USER/Documents/*/hashtable.cpython-38-darwin.so
0x113ccc000 - 0x113d33ff3 +lib.cpython-38-darwin.so (0) <0A3B0B6F-2F93-32C0-A74B-FFED79B2E54B> /Users/USER/Documents/*/lib.cpython-38-darwin.so
0x113db6000 - 0x113deffff +tslib.cpython-38-darwin.so (0) <41258659-4946-3202-BA99-2E644CE4F544> /Users/USER/Documents/*/tslib.cpython-38-darwin.so
0x113e0e000 - 0x113f0afff +interval.cpython-38-darwin.so (0) <FA90D62C-FBEA-3F01-8C36-391005D694D9> /Users/USER/Documents/*/interval.cpython-38-darwin.so
0x113f6e000 - 0x1140d4ffb +algos.cpython-38-darwin.so (0) <22712389-74EF-3891-A5EE-1753D63C2C54> /Users/USER/Documents/*/algos.cpython-38-darwin.so
0x114201000 - 0x114201fff +_opcode.cpython-38-darwin.so (0) <E82DB906-779B-3162-9B7D-04FF6CC6EED4> /Library/Frameworks/Python.framework/Versions/3.8/lib/python3.8/lib-dynload/_opcode.cpython-38-darwin.so
0x114209000 - 0x114211fff +properties.cpython-38-darwin.so (0) <AF8BF6F1-D79B-3243-BBB4-F93AAF2E1825> /Users/USER/Documents/*/properties.cpython-38-darwin.so
0x11421b000 - 0x114237ff3 +hashing.cpython-38-darwin.so (0) <6711E6B7-6AC6-3D45-8ED8-750A0952F7CD> /Users/USER/Documents/*/hashing.cpython-38-darwin.so
0x1142cb000 - 0x1142f1ffb +ops.cpython-38-darwin.so (0) <A512B9EB-4ACC-3EBE-BE79-9DAF5FF831BA> /Users/USER/Documents/*/ops.cpython-38-darwin.so
0x114449000 - 0x1144caff7 +index.cpython-38-darwin.so (0) <9A1767F7-A882-3A58-BB3B-CE843FC65A47> /Users/USER/Documents/*/index.cpython-38-darwin.so
0x11458a000 - 0x114657ff3 +sparse.cpython-38-darwin.so (0) <B09ECC25-882B-3AEE-AE32-275FCA76AD9C> /Users/USER/Documents/*/sparse.cpython-38-darwin.so
0x1147a5000 - 0x11480f70f dyld (655.1.1) <DFC3C4AF-6F97-3B34-B18D-7DCB23F2A83A> /usr/lib/dyld
0x118870000 - 0x118ac7fff +join.cpython-38-darwin.so (0) <A4F15B06-9071-3D5C-8CA9-72C23B280669> /Users/USER/Documents/*/join.cpython-38-darwin.so
0x118b8d000 - 0x118b92fff +_json.cpython-38-darwin.so (0) <E384F6C8-A33E-3A62-96E8-EE60BBBD8475> /Library/Frameworks/Python.framework/Versions/3.8/lib/python3.8/lib-dynload/_json.cpython-38-darwin.so
0x118c5c000 - 0x118c61ff3 +indexing.cpython-38-darwin.so (0) <CD00DC34-39D6-32F0-A907-2DD53B94FBCB> /Users/USER/Documents/*/indexing.cpython-38-darwin.so
0x118ca8000 - 0x118cc9ff7 +writers.cpython-38-darwin.so (0) <D3252217-5EBB-3E67-BC6A-5A360AB7EEA3> /Users/USER/Documents/*/writers.cpython-38-darwin.so
0x118ce1000 - 0x118d0effb +internals.cpython-38-darwin.so (0) <5209610D-9706-3568-A7F3-5577C7A207C1> /Users/USER/Documents/*/internals.cpython-38-darwin.so
0x118d6a000 - 0x118e6eff7 +unicodedata.cpython-38-darwin.so (0) <F6A286EE-CDEF-3F01-8C22-D4B3A83A8EEC> /Library/Frameworks/Python.framework/Versions/3.8/lib/python3.8/lib-dynload/unicodedata.cpython-38-darwin.so
0x118e7c000 - 0x118e7eff7 +mmap.cpython-38-darwin.so (0) <E367DB4B-1C06-3978-8C2D-0FE39AA5D2C9> /Library/Frameworks/Python.framework/Versions/3.8/lib/python3.8/lib-dynload/mmap.cpython-38-darwin.so
0x118f07000 - 0x118f35ff7 +reshape.cpython-38-darwin.so (0) <F5C72F85-C46D-3BC0-B71C-AC9B07E050BF> /Users/USER/Documents/*/reshape.cpython-38-darwin.so
0x118f8e000 - 0x118fdaffb +aggregations.cpython-38-darwin.so (0) <2B6F8AEB-941C-36BF-BEEF-131623FBF9A7> /Users/USER/Documents/*/aggregations.cpython-38-darwin.so
0x119006000 - 0x119021ff3 +indexers.cpython-38-darwin.so (0) <461D3133-F740-3F4A-9707-FC76ED77139E> /Users/USER/Documents/*/indexers.cpython-38-darwin.so
0x1190b4000 - 0x1191bfffb +groupby.cpython-38-darwin.so (0) <3A01AED8-EF3A-3474-9B7B-EEA3E12B7810> /Users/USER/Documents/*/groupby.cpython-38-darwin.so
0x119209000 - 0x119249ff7 +reduction.cpython-38-darwin.so (0) <28E11A6A-5FD4-3F5A-8759-C19A2F9804F5> /Users/USER/Documents/*/reduction.cpython-38-darwin.so
0x11932c000 - 0x119392fff +parsers.cpython-38-darwin.so (0) <5973B3AF-CBE5-3D76-A643-759C7358627C> /Users/USER/Documents/*/parsers.cpython-38-darwin.so
0x1193cd000 - 0x1193d1fff +_csv.cpython-38-darwin.so (0) <FF561709-D60C-308C-AC90-83E1CE7C8B16> /Library/Frameworks/Python.framework/Versions/3.8/lib/python3.8/lib-dynload/_csv.cpython-38-darwin.so
0x11941b000 - 0x119429ff3 +json.cpython-38-darwin.so (0) <976F3348-FB51-3E2C-992A-0F0F87F483E4> /Users/USER/Documents/*/json.cpython-38-darwin.so
0x1196b4000 - 0x1196c3ff7 +testing.cpython-38-darwin.so (0) <DEDECCFE-AD88-3012-B3A8-1E53CAB892C4> /Users/USER/Documents/*/testing.cpython-38-darwin.so
0x119b17000 - 0x119b72fe7 +libgmp.10.dylib (0) <8C26A0B9-4BBE-3ADE-874C-46A86C01AA91> /usr/local/opt/gmp/lib/libgmp.10.dylib
0x11b2d7000 - 0x11b8d6ff3 +cbc-c-darwin-x86-64.dylib (0) <D25C2FCE-AB81-3B77-83F5-3A0C26BF3F03> /Users/USER/Documents/*/cbc-c-darwin-x86-64.dylib
0x7fff4d627000 - 0x7fff4d8a0ff3 libBLAS.dylib (1243.200.4) <417CA0FC-B6CB-3FB3-ACBC-8914E3F62D20> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libBLAS.dylib
0x7fff4d914000 - 0x7fff4dcbdff3 libLAPACK.dylib (1243.200.4) <92175DF4-863A-3780-909A-A3E5C410F2E9> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libLAPACK.dylib
0x7fff50b92000 - 0x7fff50fd6fe7 com.apple.CoreFoundation (6.9 - 1575.19) <B2850F42-CE01-3156-B121-FD4777290C8F> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
0x7fff796c9000 - 0x7fff796caffb libDiagnosticMessagesClient.dylib (107) <A14D0819-0970-34CD-8680-80E4D7FE8C2C> /usr/lib/libDiagnosticMessagesClient.dylib
0x7fff79b09000 - 0x7fff79b0affb libSystem.B.dylib (1252.250.1) <B1006948-7AD0-3CA9-81E0-833F4DD6BFB4> /usr/lib/libSystem.B.dylib
0x7fff79d3e000 - 0x7fff79d4bfff libbz2.1.0.dylib (38.200.3) <272953A1-8D36-329B-BDDB-E887B347710F> /usr/lib/libbz2.1.0.dylib
0x7fff79d4c000 - 0x7fff79d9fff7 libc++.1.dylib (400.9.4) <9A60A190-6C34-339F-BB3D-AACE942009A4> /usr/lib/libc++.1.dylib
0x7fff79da0000 - 0x7fff79db5ff7 libc++abi.dylib (400.17) <38C09CED-9090-3719-90F3-04A2749F5428> /usr/lib/libc++abi.dylib
0x7fff7a685000 - 0x7fff7a6a2ff7 libedit.3.dylib (50.200.2) <8FBA9760-CFF6-3F53-8DBE-AEC526337D7A> /usr/lib/libedit.3.dylib
0x7fff7a6cb000 - 0x7fff7a6ccfff libffi.dylib (18.1) <DA1198F8-9789-3F16-BF60-9DA170519295> /usr/lib/libffi.dylib
0x7fff7a7fc000 - 0x7fff7aa5dffb libicucore.A.dylib (62141.0.1) <A0D63918-76E9-3C1B-B255-46F4C1DA7FE8> /usr/lib/libicucore.A.dylib
0x7fff7ad8a000 - 0x7fff7adbafff libncurses.5.4.dylib (53.200.3) <767B4D3D-CF4C-33DF-B282-0CAC013A7AD0> /usr/lib/libncurses.5.4.dylib
0x7fff7b340000 - 0x7fff7bac5fdf libobjc.A.dylib (756.2) <7C312627-43CB-3234-9324-4DEA92D59F50> /usr/lib/libobjc.A.dylib
0x7fff7c1af000 - 0x7fff7c1c1ff7 libz.1.dylib (70.200.4) <B048FC1F-058F-3A08-A1FE-81D5308CB3E6> /usr/lib/libz.1.dylib
0x7fff7c9a5000 - 0x7fff7c9a9ff3 libcache.dylib (81) <1987D1E1-DB11-3291-B12A-EBD55848E02D> /usr/lib/system/libcache.dylib
0x7fff7c9aa000 - 0x7fff7c9b4ff3 libcommonCrypto.dylib (60118.250.2) <1765BB6E-6784-3653-B16B-CB839721DC9A> /usr/lib/system/libcommonCrypto.dylib
0x7fff7c9b5000 - 0x7fff7c9bcff7 libcompiler_rt.dylib (63.4) <5212BA7B-B7EA-37B4-AF6E-AC4F507EDFB8> /usr/lib/system/libcompiler_rt.dylib
0x7fff7c9bd000 - 0x7fff7c9c6ff7 libcopyfile.dylib (146.250.1) <98CD00CD-9B91-3B5C-A9DB-842638050FA8> /usr/lib/system/libcopyfile.dylib
0x7fff7c9c7000 - 0x7fff7ca4bfc3 libcorecrypto.dylib (602.260.2) <01464D24-570C-3B83-9D18-467769E0FCDD> /usr/lib/system/libcorecrypto.dylib
0x7fff7cad2000 - 0x7fff7cb0bff7 libdispatch.dylib (1008.270.1) <97273678-E94C-3C8C-89F6-2E2020F4B43B> /usr/lib/system/libdispatch.dylib
0x7fff7cb0c000 - 0x7fff7cb38ff7 libdyld.dylib (655.1.1) <002418CC-AD11-3D10-865B-015591D24E6C> /usr/lib/system/libdyld.dylib
0x7fff7cb39000 - 0x7fff7cb39ffb libkeymgr.dylib (30) <0D0F9CA2-8D5A-3273-8723-59987B5827F2> /usr/lib/system/libkeymgr.dylib
0x7fff7cb47000 - 0x7fff7cb47ff7 liblaunch.dylib (1336.261.2) <2B07E27E-D404-3E98-9D28-BCA641E5C479> /usr/lib/system/liblaunch.dylib
0x7fff7cb48000 - 0x7fff7cb4dfff libmacho.dylib (927.0.3) <A377D608-77AB-3F6E-90F0-B4F251A5C12F> /usr/lib/system/libmacho.dylib
0x7fff7cb4e000 - 0x7fff7cb50ffb libquarantine.dylib (86.220.1) <6D0BC770-7348-3608-9254-F7FFBD347634> /usr/lib/system/libquarantine.dylib
0x7fff7cb51000 - 0x7fff7cb52ff7 libremovefile.dylib (45.200.2) <9FBEB2FF-EEBE-31BC-BCFC-C71F8D0E99B6> /usr/lib/system/libremovefile.dylib
0x7fff7cb53000 - 0x7fff7cb6aff3 libsystem_asl.dylib (356.200.4) <A62A7249-38B8-33FA-9875-F1852590796C> /usr/lib/system/libsystem_asl.dylib
0x7fff7cb6b000 - 0x7fff7cb6bff7 libsystem_blocks.dylib (73) <A453E8EE-860D-3CED-B5DC-BE54E9DB4348> /usr/lib/system/libsystem_blocks.dylib
0x7fff7cb6c000 - 0x7fff7cbf3fff libsystem_c.dylib (1272.250.1) <7EDACF78-2FA3-35B8-B051-D70475A35117> /usr/lib/system/libsystem_c.dylib
0x7fff7cbf4000 - 0x7fff7cbf7ffb libsystem_configuration.dylib (963.270.3) <2B4A836D-68A4-33E6-8D48-CD4486B03387> /usr/lib/system/libsystem_configuration.dylib
0x7fff7cbf8000 - 0x7fff7cbfbff7 libsystem_coreservices.dylib (66) <719F75A4-74C5-3BA6-A09E-0C5A3E5889D7> /usr/lib/system/libsystem_coreservices.dylib
0x7fff7cbfc000 - 0x7fff7cc02fff libsystem_darwin.dylib (1272.250.1) <EC9B39A5-9592-3577-8997-7DC721D20D8C> /usr/lib/system/libsystem_darwin.dylib
0x7fff7cc03000 - 0x7fff7cc09ff7 libsystem_dnssd.dylib (878.270.2) <E9A5ACCF-E35F-3909-AF0A-2A37CD217276> /usr/lib/system/libsystem_dnssd.dylib
0x7fff7cc0a000 - 0x7fff7cc55ffb libsystem_info.dylib (517.200.9) <D09D5AE0-2FDC-3A6D-93EC-729F931B1457> /usr/lib/system/libsystem_info.dylib
0x7fff7cc56000 - 0x7fff7cc7eff7 libsystem_kernel.dylib (4903.271.2) <EA204E3C-870B-30DD-B4AF-D1BB66420D14> /usr/lib/system/libsystem_kernel.dylib
0x7fff7cc7f000 - 0x7fff7cccaff7 libsystem_m.dylib (3158.200.7) <F19B6DB7-014F-3820-831F-389CCDA06EF6> /usr/lib/system/libsystem_m.dylib
0x7fff7cccb000 - 0x7fff7ccf5fff libsystem_malloc.dylib (166.270.1) <011F3AD0-8E6A-3A89-AE64-6E5F6840F30A> /usr/lib/system/libsystem_malloc.dylib
0x7fff7ccf6000 - 0x7fff7cd00ff7 libsystem_networkextension.dylib (767.250.2) <FF06F13A-AEFE-3A27-A073-910EF78AEA36> /usr/lib/system/libsystem_networkextension.dylib
0x7fff7cd01000 - 0x7fff7cd08fff libsystem_notify.dylib (172.200.21) <145B5CFC-CF73-33CE-BD3D-E8DDE268FFDE> /usr/lib/system/libsystem_notify.dylib
0x7fff7cd09000 - 0x7fff7cd12fef libsystem_platform.dylib (177.270.1) <9D1FE5E4-EB7D-3B3F-A8D1-A96D9CF1348C> /usr/lib/system/libsystem_platform.dylib
0x7fff7cd13000 - 0x7fff7cd1dff7 libsystem_pthread.dylib (330.250.2) <2D5C08FF-484F-3D59-9132-CE1DCB3F76D7> /usr/lib/system/libsystem_pthread.dylib
0x7fff7cd1e000 - 0x7fff7cd21ff7 libsystem_sandbox.dylib (851.270.1) <9494594B-5199-3186-82AB-5FF8BED6EE16> /usr/lib/system/libsystem_sandbox.dylib
0x7fff7cd22000 - 0x7fff7cd24ff3 libsystem_secinit.dylib (30.260.2) <EF1EA47B-7B22-35E8-BD9B-F7003DCB96AE> /usr/lib/system/libsystem_secinit.dylib
0x7fff7cd25000 - 0x7fff7cd2cff3 libsystem_symptoms.dylib (820.267.1) <03F1C2DD-0F5A-3D9D-88F6-B26C0F94EB52> /usr/lib/system/libsystem_symptoms.dylib
0x7fff7cd2d000 - 0x7fff7cd42fff libsystem_trace.dylib (906.260.1) <FC761C3B-5434-3A52-912D-F1B15FAA8EB2> /usr/lib/system/libsystem_trace.dylib
0x7fff7cd44000 - 0x7fff7cd49ffb libunwind.dylib (35.4) <24A97A67-F017-3CFC-B0D0-6BD0224B1336> /usr/lib/system/libunwind.dylib
0x7fff7cd4a000 - 0x7fff7cd79fff libxpc.dylib (1336.261.2) <7DEE2300-6D8E-3C00-9C63-E3E80D56B0C4> /usr/lib/system/libxpc.dylib
External Modification Summary:
Calls made by other processes targeting this process:
task_for_pid: 0
thread_create: 0
thread_set_state: 0
Calls made by this process:
task_for_pid: 0
thread_create: 0
thread_set_state: 0
Calls made by all processes on this machine:
task_for_pid: 24964
thread_create: 0
thread_set_state: 0
VM Region Summary:
ReadOnly portion of Libraries: Total=351.7M resident=0K(0%) swapped_out_or_unallocated=351.7M(100%)
Writable regions: Total=273.6M written=0K(0%) resident=0K(0%) swapped_out=0K(0%) unallocated=273.6M(100%)
VIRTUAL REGION
REGION TYPE SIZE COUNT (non-coalesced)
=========== ======= =======
Dispatch continuations 16.0M 1
Kernel Alloc Once 8K 1
MALLOC 141.9M 68
MALLOC guard page 16K 3
MALLOC_LARGE (reserved) 256K 1 reserved VM address space (unallocated)
STACK GUARD 24K 6
Stack 18.5M 6
VM_ALLOCATE 4K 1
VM_ALLOCATE (reserved) 96.0M 2 reserved VM address space (unallocated)
__DATA 6528K 183
__DATA_CONST 72K 1
__LINKEDIT 234.9M 94
__TEXT 116.8M 140
__UNICODE 564K 1
shared memory 12K 3
=========== ======= =======
TOTAL 631.5M 511
TOTAL, minus reserved VM space 535.3M 511
Model: MacBookPro15,2, BootROM 1037.60.58.0.0 (iBridge: 17.16.12551.0.0,0), 4 processors, Intel Core i7, 2.8 GHz, 16 GB, SMC
Graphics: kHW_IntelIrisGraphics655Item, Intel Iris Plus Graphics 655, spdisplays_builtin
Memory Module: BANK 0/ChannelA-DIMM0, 8 GB, LPDDR3, 2133 MHz, Micron, -
Memory Module: BANK 2/ChannelB-DIMM0, 8 GB, LPDDR3, 2133 MHz, Micron, -
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x7BF), wl0: Mar 28 2019 19:17:52 version 9.137.9.0.32.6.34 FWID 01-36f56c94
Bluetooth: Version 6.0.14d3, 3 services, 18 devices, 1 incoming serial ports
Network Service: Wi-Fi, AirPort, en0
USB Device: USB 3.1 Bus
USB Device: iBridge Bus
USB Device: Touch Bar Backlight
USB Device: Touch Bar Display
USB Device: Apple Internal Keyboard / Trackpad
USB Device: Headset
USB Device: Ambient Light Sensor
USB Device: FaceTime HD Camera (Built-in)
USB Device: Apple T2 Controller
Thunderbolt Bus: MacBook Pro, Apple Inc., 41.2
Thunderbolt Bus: MacBook Pro, Apple Inc., 41.2
Today We are Going To Solve Process finished with exit code 139 (interrupted by signal 11: SIGSEGV) in Python. Here we will Discuss All Possible Solutions and How this error Occurs So let’s get started with this Article.
Contents
- 1 How to Fix Process finished with exit code 139 (interrupted by signal 11: SIGSEGV) Error?
- 1.1 Solution 1 : Use gdb commands
- 1.2 Solution 2 : Downgrade the TensorFlow version to 1.4
- 1.3 Solution 3 : Replace cv2.SIFT()
- 1.4 Solution 4 : Delete the python interpreter and the ‘venv’ folder
- 2 Conclusion
- 2.1 Also Read These Solutions
- How to Fix Process finished with exit code 139 (interrupted by signal 11: SIGSEGV) Error?
To Fix Process finished with exit code 139 (interrupted by signal 11: SIGSEGV) Error just Use gdb commands. First of all, just use it to run your Python program:
gdb --args python <more args if you want>And then use gdb commands to track down the problem. It will help you. - Process finished with exit code 139 (interrupted by signal 11: SIGSEGV)
To Fix Process finished with exit code 139 (interrupted by signal 11: SIGSEGV) Error just Downgrade the TensorFlow version to 1.4. If you are using TensorFlow then just simply downgrade the TensorFlow version to 1.4. It will help you.
Solution 1 : Use gdb commands
First of all, just use it to run your Python program:
gdb --args python <more args if you want>And then use gdb commands to track down the problem. It will help you.
Solution 2 : Downgrade the TensorFlow version to 1.4
If you are using TensorFlow then just simply downgrade the TensorFlow version to 1.4. It will help you.
Solution 3 : Replace cv2.SIFT()
If you are using OpenCV library to apply SIFT. Then just replace cv2.SIFT() to cv2.SIFT_create(). It will remove the error.
Solution 4 : Delete the python interpreter and the ‘venv’ folder
To solve this issue just Delete the python interpreter and the ‘venv’ folder. By deleting this your code will work fine.
Conclusion
So these were all possible solutions to this error. I hope your error has been solved by this article. In the comments, tell us which solution worked? If you liked our article, please share it on your social media and comment on your suggestions. Thank you.
Also Read These Solutions
- URL scheme must be “http” or “https” for CORS request
- RuntimeError: CUDA out of memory. Tried to allocate
- Command “python setup.py egg_info” failed with error code 1
- Module was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.5.1, expected version is 1.1.15
- Error: A non-null value must be returned since the return type ‘Never’ doesn’t allow null
Hello Guys, How are you all? Hope You all Are Fine. Today I am trying to run my python script but I am facing following error Process finished with exit code 139 (interrupted by signal 11: SIGSEGV) in Python. So Here I am Explain to you all the possible solutions here.
Without wasting your time, Let’s start This Article to Solve This Error.
Contents
- How Process finished with exit code 139 (interrupted by signal 11: SIGSEGV) Error Occurs ?
- How To Solve Process finished with exit code 139 (interrupted by signal 11: SIGSEGV) Error ?
- Solution 1: Follow this solution
- Summary
I am trying to run my python script but I am facing following error.
Process finished with exit code 139 (interrupted by signal 11: SIGSEGV)How To Solve Process finished with exit code 139 (interrupted by signal 11: SIGSEGV) Error ?
- How To Solve Process finished with exit code 139 (interrupted by signal 11: SIGSEGV) Error?
To Solve Process finished with exit code 139 (interrupted by signal 11: SIGSEGV) Error Here you’re trying to read/write a file which is open. In this case, simply closing the file and rerunning the script solved the issue. So That just close the file that you are trying to read or write and then run your script.
- Process finished with exit code 139 (interrupted by signal 11: SIGSEGV)
To Solve Process finished with exit code 139 (interrupted by signal 11: SIGSEGV) Error Here you’re trying to read/write a file which is open. In this case, simply closing the file and rerunning the script solved the issue. So That just close the file that you are trying to read or write and then run your script.
Solution 1: Follow this solution
Here you’re trying to read/write a file which is open. In this case, simply closing the file and rerunning the script solved the issue. So That just close the file that you are trying to read or write and then run your script.
Summary
It’s all About this issue. Hope all solution helped you a lot. Comment below Your thoughts and your queries. Also, Comment below which solution worked for you?
Also, Read
- ModuleNotFoundError: No module named ‘utils’
How to fix the Runtime Code 139 Minecraft Error 139
This article features error number Code 139, commonly known as Minecraft Error 139 described as Game ended with bad state (exit code 139).
About Runtime Code 139
Runtime Code 139 happens when Minecraft fails or crashes whilst it’s running, hence its name. It doesn’t necessarily mean that the code was corrupt in some way, but just that it did not work during its run-time. This kind of error will appear as an annoying notification on your screen unless handled and corrected. Here are symptoms, causes and ways to troubleshoot the problem.
Definitions (Beta)
Here we list some definitions for the words contained in your error, in an attempt to help you understand your problem. This is a work in progress, so sometimes we might define the word incorrectly, so feel free to skip this section!
- Exit — Exiting, quitting, or halting refers to the termination of a process or program.
- Exit code — An exit code is signaled by a program on termination to indicate if it completed successfully, or, if it did not, what sort of failure condition occurred.
- Minecraft — A voxel-based sandbox game coded in Java by Mojang where players place and destroy blocks to gain armor, weapons and tools in a randomly generated world
- State — A design pattern used to represent the state of an object
Symptoms of Code 139 — Minecraft Error 139
Runtime errors happen without warning. The error message can come up the screen anytime Minecraft is run. In fact, the error message or some other dialogue box can come up again and again if not addressed early on.
There may be instances of files deletion or new files appearing. Though this symptom is largely due to virus infection, it can be attributed as a symptom for runtime error, as virus infection is one of the causes for runtime error. User may also experience a sudden drop in internet connection speed, yet again, this is not always the case.
(For illustrative purposes only)
Causes of Minecraft Error 139 — Code 139
During software design, programmers code anticipating the occurrence of errors. However, there are no perfect designs, as errors can be expected even with the best program design. Glitches can happen during runtime if a certain error is not experienced and addressed during design and testing.
Runtime errors are generally caused by incompatible programs running at the same time. It may also occur because of memory problem, a bad graphics driver or virus infection. Whatever the case may be, the problem must be resolved immediately to avoid further problems. Here are ways to remedy the error.
Repair Methods
Runtime errors may be annoying and persistent, but it is not totally hopeless, repairs are available. Here are ways to do it.
If a repair method works for you, please click the upvote button to the left of the answer, this will let other users know which repair method is currently working the best.
Please note: Neither ErrorVault.com nor it’s writers claim responsibility for the results of the actions taken from employing any of the repair methods listed on this page — you complete these steps at your own risk.
Method 2 — Update / Reinstall Conflicting Programs
Using Control Panel
- For Windows 7, click the Start Button, then click Control panel, then Uninstall a program
- For Windows 8, click the Start Button, then scroll down and click More Settings, then click Control panel > Uninstall a program.
- For Windows 10, just type Control Panel on the search box and click the result, then click Uninstall a program
- Once inside Programs and Features, click the problem program and click Update or Uninstall.
- If you chose to update, then you will just need to follow the prompt to complete the process, however if you chose to Uninstall, you will follow the prompt to uninstall and then re-download or use the application’s installation disk to reinstall the program.
Using Other Methods
- For Windows 7, you may find the list of all installed programs when you click Start and scroll your mouse over the list that appear on the tab. You may see on that list utility for uninstalling the program. You may go ahead and uninstall using utilities available in this tab.
- For Windows 10, you may click Start, then Settings, then choose Apps.
- Scroll down to see the list of Apps and features installed in your computer.
- Click the Program which is causing the runtime error, then you may choose to uninstall or click Advanced options to reset the application.
Method 1 — Close Conflicting Programs
When you get a runtime error, keep in mind that it is happening due to programs that are conflicting with each other. The first thing you can do to resolve the problem is to stop these conflicting programs.
- Open Task Manager by clicking Ctrl-Alt-Del at the same time. This will let you see the list of programs currently running.
- Go to the Processes tab and stop the programs one by one by highlighting each program and clicking the End Process buttom.
- You will need to observe if the error message will reoccur each time you stop a process.
- Once you get to identify which program is causing the error, you may go ahead with the next troubleshooting step, reinstalling the application.
Method 3 — Update your Virus protection program or download and install the latest Windows Update
Virus infection causing runtime error on your computer must immediately be prevented, quarantined or deleted. Make sure you update your virus program and run a thorough scan of the computer or, run Windows update so you can get the latest virus definition and fix.
Method 4 — Re-install Runtime Libraries
You might be getting the error because of an update, like the MS Visual C++ package which might not be installed properly or completely. What you can do then is to uninstall the current package and install a fresh copy.
- Uninstall the package by going to Programs and Features, find and highlight the Microsoft Visual C++ Redistributable Package.
- Click Uninstall on top of the list, and when it is done, reboot your computer.
- Download the latest redistributable package from Microsoft then install it.
Method 5 — Run Disk Cleanup
You might also be experiencing runtime error because of a very low free space on your computer.
- You should consider backing up your files and freeing up space on your hard drive
- You can also clear your cache and reboot your computer
- You can also run Disk Cleanup, open your explorer window and right click your main directory (this is usually C: )
- Click Properties and then click Disk Cleanup
Method 6 — Reinstall Your Graphics Driver
If the error is related to a bad graphics driver, then you may do the following:
- Open your Device Manager, locate the graphics driver
- Right click the video card driver then click uninstall, then restart your computer
Method 7 — IE related Runtime Error
If the error you are getting is related to the Internet Explorer, you may do the following:
- Reset your browser.
- For Windows 7, you may click Start, go to Control Panel, then click Internet Options on the left side. Then you can click Advanced tab then click the Reset button.
- For Windows 8 and 10, you may click search and type Internet Options, then go to Advanced tab and click Reset.
- Disable script debugging and error notifications.
- On the same Internet Options window, you may go to Advanced tab and look for Disable script debugging
- Put a check mark on the radio button
- At the same time, uncheck the «Display a Notification about every Script Error» item and then click Apply and OK, then reboot your computer.
If these quick fixes do not work, you can always backup files and run repair reinstall on your computer. However, you can do that later when the solutions listed here did not do the job.
Other languages:
Wie beheben Fehler 139 (Minecraft-Fehler 139) — Spiel mit schlechtem Status beendet (Exitcode 139).
Come fissare Errore 139 (Errore Minecraft 139) — Il gioco è terminato con un cattivo stato (codice di uscita 139).
Hoe maak je Fout 139 (Minecraft-fout 139) — Spel eindigde met slechte staat (afsluitcode 139).
Comment réparer Erreur 139 (Erreur Minecraft 139) — Le jeu s’est terminé avec un mauvais état (code de sortie 139).
어떻게 고치는 지 오류 139 (마인크래프트 오류 139) — 게임이 잘못된 상태로 종료되었습니다(종료 코드 139).
Como corrigir o Erro 139 (Minecraft Error 139) — O jogo terminou em mau estado (código de saída 139).
Hur man åtgärdar Fel 139 (Minecraft fel 139) — Spelet slutade med dåligt tillstånd (utgångskod 139).
Как исправить Ошибка 139 (Ошибка Minecraft 139) — Игра закончилась с плохим состоянием (код выхода 139).
Jak naprawić Błąd 139 (Błąd Minecrafta 139) — Gra zakończyła się złym stanem (kod wyjścia 139).
Cómo arreglar Error 139 (Error 139 de Minecraft) — El juego terminó en mal estado (código de salida 139).
About The Author: Phil Hart has been a Microsoft Community Contributor since 2010. With a current point score over 100,000, they’ve contributed more than 3000 answers in the Microsoft Support forums and have created almost 200 new help articles in the Technet Wiki.
Follow Us: 
Last Updated:
21/11/22 06:42 : A Windows 10 user voted that repair method 2 worked for them.
This repair tool can fix common computer problems such as blue screens, crashes and freezes, missing DLL files, as well as repair malware/virus damage and more by replacing damaged and missing system files.
STEP 1:
Click Here to Download and install the Windows repair tool.
STEP 2:
Click on Start Scan and let it analyze your device.
STEP 3:
Click on Repair All to fix all of the issues it detected.
DOWNLOAD NOW
Compatibility
Requirements
1 Ghz CPU, 512 MB RAM, 40 GB HDD
This download offers unlimited scans of your Windows PC for free. Full system repairs start at $19.95.
Article ID: ACX08376EN
Applies To: Windows 10, Windows 8.1, Windows 7, Windows Vista, Windows XP, Windows 2000
Speed Up Tip #50
Convert Windows into a Virtual Machine:
Save yourself from malware, spyware, and other viruses by converting your Windows PC into a Virtual Machine. Browse the internet or install any program and games you want with confidence in your Virtual Machine by using free tools like Hyper-V. Your host operating system will be safe from troubles.
Click Here for another way to speed up your Windows PC
Microsoft & Windows® logos are registered trademarks of Microsoft. Disclaimer: ErrorVault.com is not affiliated with Microsoft, nor does it claim such affiliation. This page may contain definitions from https://stackoverflow.com/tags under the CC-BY-SA license. The information on this page is provided for informational purposes only. © Copyright 2018