# Gromacs 2023: Segmentation fault with gmx anaeig (but no problem with Gromacs 2022.4)

**URL:** <https://gromacs.bioexcel.eu/t/gromacs-2023-segmentation-fault-with-gmx-anaeig-but-no-problem-with-gromacs-2022-4/6062>\
**Category:** User discussions\
**Tags:** analysis-tools\
**Created:** [March 28, 2023, 5:24am UTC](https://gromacs.bioexcel.eu/t/gromacs-2023-segmentation-fault-with-gmx-anaeig-but-no-problem-with-gromacs-2022-4/6062 "2023-03-28T05:24:24Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![asimbepari](https://avatars.discourse-cdn.com/v4/letter/a/9dc877/32.png) [@asimbepari](https://gromacs.bioexcel.eu/u/asimbepari)\
**Post date:** [March 28, 2023, 5:24am UTC](https://gromacs.bioexcel.eu/t/gromacs-2023-segmentation-fault-with-gmx-anaeig-but-no-problem-with-gromacs-2022-4/6062/1 "2023-03-28T05:24:24Z")

</div>

## GROMACS version: 2023 GROMACS modification: No Here post your question I appreciate your help. Thanks in advance. I get error with Gromacs 2023. However, I get the command done successfully in previous Gromacs versions (including 2022.4) for the same system. Files are added (link provided).

echo C-alpha C-alpha | gmx anaeig -s md\_sim.tpr -f md\_sim\_1.xtc -proj -first 1 -last 6  
:-) GROMACS - gmx anaeig, 2023 (-:

Executable: /mnt/l/Software/Gromacs-2023/bin/gmx  
Data prefix: /mnt/l/Software/Gromacs-2023  
Working dir: /mnt/c/Users/USER/Downloads/anaeig-test  
Command line:  
gmx anaeig -s md\_sim.tpr -f md\_sim\_1.xtc -proj -first 1 -last 6

## Segmentation fault

Link for files:  
[Gromacs-2023-gmx-anaeig-segmentation-fault](https://drive.google.com/drive/folders/15-KUlkph1mBqZWPUNMhPUvjo__EUelPh?usp=share_link)

---

<div class="post-metadata">

**Author:** ![al42and](https://dub1.discourse-cdn.com/flex017/user_avatar/gromacs.bioexcel.eu/al42and/32/1393_2.png) [@al42and](https://gromacs.bioexcel.eu/u/al42and)\
**Post date:** [March 28, 2023, 11:42am UTC](https://gromacs.bioexcel.eu/t/gromacs-2023-segmentation-fault-with-gmx-anaeig-but-no-problem-with-gromacs-2022-4/6062/2 "2023-03-28T11:42:09Z")

</div>

Hi! Thank you for reporting.

That’s indeed a bug in GROMACS 2023. I opened an issue to track it, [Segfaults due to calling fn2ftp(nullptr) (#4756) · Issues · GROMACS / GROMACS · GitLab](https://gitlab.com/gromacs/gromacs/-/issues/4756).

We’ll fix it in 2023.1 or 2023.2. I expect you don’t need an urgent workaround and can just use 2022.x for your analysis?

---

<div class="post-metadata">

**Author:** ![asimbepari](https://avatars.discourse-cdn.com/v4/letter/a/9dc877/32.png) [@asimbepari](https://gromacs.bioexcel.eu/u/asimbepari)\
**Post date:** [March 28, 2023, 12:01pm UTC](https://gromacs.bioexcel.eu/t/gromacs-2023-segmentation-fault-with-gmx-anaeig-but-no-problem-with-gromacs-2022-4/6062/3 "2023-03-28T12:01:22Z")

</div>

Thanks a lot.  
I was feeling very happy with Gromacs 2023!  
I am getting 2X simulation speed (~300 ns/day for the system I mentioned) compared to Gromacs 2022.4.  
I will wait for a fix.

---

<div class="post-metadata">

**Author:** ![al42and](https://dub1.discourse-cdn.com/flex017/user_avatar/gromacs.bioexcel.eu/al42and/32/1393_2.png) [@al42and](https://gromacs.bioexcel.eu/u/al42and)\
**Post date:** [March 28, 2023, 12:21pm UTC](https://gromacs.bioexcel.eu/t/gromacs-2023-segmentation-fault-with-gmx-anaeig-but-no-problem-with-gromacs-2022-4/6062/4 "2023-03-28T12:21:33Z")

</div>

As a workaround, you can add `-3d temp3d.gro` to your command. It will cause extra work, especially for long trajectories, but it should not crash.

---

<div class="post-metadata">

**Author:** ![asimbepari](https://avatars.discourse-cdn.com/v4/letter/a/9dc877/32.png) [@asimbepari](https://gromacs.bioexcel.eu/u/asimbepari)\
**Post date:** [March 28, 2023, 3:03pm UTC](https://gromacs.bioexcel.eu/t/gromacs-2023-segmentation-fault-with-gmx-anaeig-but-no-problem-with-gromacs-2022-4/6062/5 "2023-03-28T15:03:35Z")

</div>

Thank you very much!  
I am asking for another help. What if I want 2d projection of vector1 and vector2?  
I was using the following command:  
echo C-alpha C-alpha | gmx anaeig -s md\_sim.tpr -f md\_sim\_fit.xtc -2d -first 1 -last 2

---

<div class="post-metadata">

**Author:** ![nilanjana88](https://avatars.discourse-cdn.com/v4/letter/n/59ef9b/32.png) [@nilanjana88](https://gromacs.bioexcel.eu/u/nilanjana88)\
**Post date:** [January 7, 2025, 11:37am UTC](https://gromacs.bioexcel.eu/t/gromacs-2023-segmentation-fault-with-gmx-anaeig-but-no-problem-with-gromacs-2022-4/6062/6 "2025-01-07T11:37:16Z")

</div>

Hi!  
Is this issue solved?  
Because I’m getting a similar error in Gromacs 2023.

Command line:  
gmx anaeig -v eigenvec.trr -f md\_0\_2\_center.xtc -s md\_0\_2.tpr -proj proj.xvg -2d 2dproj.xvg -extr extreme.pdb -filt filtered.xtc -first 1 -last 2

Segmentation fault (core dumped)

---

<div class="post-metadata">

**Author:** ![hess](https://dub1.discourse-cdn.com/flex017/user_avatar/gromacs.bioexcel.eu/hess/32/416_2.png) [@hess](https://gromacs.bioexcel.eu/u/hess)\
**Post date:** [January 9, 2025, 8:48am UTC](https://gromacs.bioexcel.eu/t/gromacs-2023-segmentation-fault-with-gmx-anaeig-but-no-problem-with-gromacs-2022-4/6062/7 "2025-01-09T08:48:37Z")

</div>

Yes, this issue has been solved in 2023.1. I assume you are using 2023.
