Segfault in ThermodynamicState._find_thermostat()
See original GitHub issueI just ran into this weird (stochastic?) segfault during a travis test:
ThermodynamicState._find_thermostat() method. ... *** glibc detected *** /home/travis/miniconda/envs/test/bin/python: corrupted double-linked list: 0x00000000131c0830 ***
Issue Analytics
- State:
- Created 6 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
Identify what's causing segmentation faults (segfaults)
A segmentation fault (aka segfault) is a common condition that causes programs to crash; they are often associated with a file named core...
Read more >c++ - What is a segmentation fault?
A segmentation fault occurs when a program attempts to access a memory location that it is not allowed to access, or attempts to...
Read more >A Guide for Troubleshooting a Segfault
A segmentation fault (also known as a segfault or a segmentation violation) occurs when a process attempts to access a memory location that ......
Read more >Segmentation fault
A segmentation fault occurs when a program attempts to access a memory location that it is not allowed to access, or attempts to...
Read more >Common Causes of Segmentation Faults (Segfaults)
A segmentation fault (often called a segfault) can occur if a program you are running attempts to access an invalid memory location.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
valgrind may come in handy if you haven’t already resorted to it.
Could be! The weird thing is that the system is used and deepcopied in several other tests as well and it works fine, so the last time I spent on this I was trying to figure out which of the previous test ends up corrupting the memory.