Tag Archives: Segment error

[Solved] paddle:FatalError: `Segmentation fault` is detected by the operating system.

Question

When using the paddle framework for relevant model training, an error is reported when using the GPU:

C++ Traceback (most recent call last):
--------------------------------------
0 std::thread::_Impl<std::_Bind_simple<ThreadPool::ThreadPool(unsigned long)::{lambda()#1} ()> >::_M_run()
1 std::__future_base::_State_baseV2::_M_do_set(std::function<std::unique_ptr<std::__future_base::_Result_base, std::__future_base::_Result_base::_Deleter> ()>*, bool*)
2 paddle::framework::SignalHandle(char const*, int)
3 paddle::platform::GetCurrentTraceBackString[abi:cxx11]()

----------------------
Error Message Summary:
----------------------
FatalError: `Segmentation fault` is detected by the operating system.
[TimeInfo: *** Aborted at 1639543591 (unix time) try "date -d @1639543591" if you are using GNU date ***]
[SignalInfo: *** SIGSEGV (@0x0) received by PID 168238 (TID 0x7fc05d8c5700) from PID 0 ***]

edition:

python=3.8 paddlepaddle-gpu=2.2.1 cuda=10.1 cudnn=7.6

Check the issue and find that many of these situations occur. Make a record here

Solution:

Reinstall using CONDA.

Execute command:

conda install paddlepaddle-gpu==2.2.1 cudatoolkit=10.1 --channel https://mirrors.tuna.tsinghua.edu.cn/anaconda/cloud/Paddle/

[Solved] Segyio Error: Runtime Error trace count inconsistent with file size, trace lengths … #401

Article catalog

Run segyio to read segy files and report errors. Troubleshooting error cause reference

An error occurs when running segyio to read the segy file

"RuntimeError: trace count inconsistent with file size, trace lengths possibly of non-uniform"

Solution:

(1) Add: endian ='little '

with segyio.open('test.sgy','r',ignore_geometry=True,endian='little') as f:

(2) If it still fails:
check the length of the data trace. Segyio’s default trace has the same number and format of sampling points. If the length of the trace in the segy file is inconsistent, it may lead to reading errors.

Error reason

Detailed explanation of big endian and little endian
the default bytes of files read by segyio are encoded according to big endian, while your files are written according to little endian bytes