# ERROR: Caught signal number 11 (Segmentation fault) at /lib/x86\_64-linux-gnu/libc.so.6(+0xb1426)\[0x7f576c0c1426\] \[0x4\]

**URL:** <https://forum.generic-mapping-tools.org/t/error-caught-signal-number-11-segmentation-fault-at-lib-x86-64-linux-gnu-libc-so-6-0xb1426-0x7f576c0c1426-0x4/1613>\
**Category:** Q&A\
**Created:** [April 28, 2021, 5:23am UTC](https://forum.generic-mapping-tools.org/t/error-caught-signal-number-11-segmentation-fault-at-lib-x86-64-linux-gnu-libc-so-6-0xb1426-0x7f576c0c1426-0x4/1613 "2021-04-28T05:23:49Z")\
**Posts on this page:** 11\
**Page:** 1

<div class="post-metadata">

**Author:** ![yomigaius](https://avatars.discourse-cdn.com/v4/letter/y/f08c70/32.png) [@yomigaius](https://forum.generic-mapping-tools.org/u/yomigaius)\
**Post date:** [April 28, 2021, 5:23am UTC](https://forum.generic-mapping-tools.org/t/error-caught-signal-number-11-segmentation-fault-at-lib-x86-64-linux-gnu-libc-so-6-0xb1426-0x7f576c0c1426-0x4/1613/1 "2021-04-28T05:23:49Z")

</div>

Hi all,

I am trying to plot a set of tangential component of receiver function, RFs, data on GMT Version 5.4.3 (r19528), but I got the lines of error message below.

Meanwhile, I had previously used the same script to plot for radial and tangential components of the same station, and it produced the plots.

The scripts to plot the radial component still works well and produce the plots. But, as I ran the scripts again on the tangential components of the RFs again for the same station and other stations, it brought out the error message.

Can you please advise? Thanks.

ERROR: Caught signal number 11 (Segmentation fault) at  
/lib/x86\_64-linux-gnu/libc.so.6(+0xb1426)[0x7f576c0c1426]  
[0x4]  
Stack backtrace:  
/usr/lib/x86\_64-linux-gnu/libgmt.so.5(sig\_handler+0x2b1)[0x7f576c64bbf1]  
/lib/x86\_64-linux-gnu/libpthread.so.0(+0x12980)[0x7f576c413980]  
/lib/x86\_64-linux-gnu/libc.so.6(+0xb1426)[0x7f576c0c1426]  
/lib/x86\_64-linux-gnu/libc.so.6(+0x5ab45)[0x7f576c06ab45]  
/lib/x86\_64-linux-gnu/libc.so.6(\_IO\_vfprintf+0x192a)[0x7f576c06cdba]  
/lib/x86\_64-linux-gnu/libc.so.6(\_\_vsnprintf\_chk+0xa9)[0x7f576c141ff9]  
/usr/lib/x86\_64-linux-gnu/libgmt.so.5(GMT\_Report+0x1a2)[0x7f576c64fba2]  
/usr/lib/x86\_64-linux-gnu/gmt/plugins/supplements.so(GMT\_pssac+0x2e6b)[0x7f5757570dcb]  
/usr/lib/x86\_64-linux-gnu/libgmt.so.5(GMT\_Call\_Module+0xc6)[0x7f576c657296]  
gmt(main+0x8ae)[0x5588496c061e]  
/lib/x86\_64-linux-gnu/libc.so.6(\_\_libc\_start\_main+0xe7)[0x7f576c031bf7]  
gmt(\_start+0x2a)[0x5588496c089a]

---

<div class="post-metadata">

**Author:** ![Andreas](https://avatars.discourse-cdn.com/v4/letter/a/ee7513/32.png) [@Andreas](https://forum.generic-mapping-tools.org/u/Andreas)\
**Post date:** [April 28, 2021, 10:58am UTC](https://forum.generic-mapping-tools.org/t/error-caught-signal-number-11-segmentation-fault-at-lib-x86-64-linux-gnu-libc-so-6-0xb1426-0x7f576c0c1426-0x4/1613/2 "2021-04-28T10:58:43Z")

</div>

> [@yomigaius](#):
>
> GMT Version 5.4.3

You’re using a very old version (GMT Version 5.4.3). You should try upgrading first, to see if the problem persists.

---

<div class="post-metadata">

**Author:** ![yomigaius](https://avatars.discourse-cdn.com/v4/letter/y/f08c70/32.png) [@yomigaius](https://forum.generic-mapping-tools.org/u/yomigaius)\
**Post date:** [April 29, 2021, 10:03am UTC](https://forum.generic-mapping-tools.org/t/error-caught-signal-number-11-segmentation-fault-at-lib-x86-64-linux-gnu-libc-so-6-0xb1426-0x7f576c0c1426-0x4/1613/3 "2021-04-29T10:03:40Z")

</div>

Thank you for the response @Andreas . I have tried running the script on GMT 6.1 and still encountered the same error message.

Please, find below the commands in the script for GMT 5.4

cd SAC/for\_receiver  
gmt psbasemap -R-5/30/0.035/0.085 -JX2i/3i -B5f1:“Time (s)”:/0.005f0.001:“p (s/km)”:WenS -K -P -X2i \> rf\_zi.ps  
gmt pssac \*.zi -R -JX -B -W0.5p -M0.3 -Eu4 -K -P -O \>\>rf\_zi.ps

ps2pdf rf\_zi.ps  
evince rf\_zi.pdf

I have also adapted the script to GMT 6.1 format and ran on same, but I still got the same error message.

I do hope I can find helpful suggestions.  
Thanks.

'Yomi Gaius

---

<div class="post-metadata">

**Author:** ![Joaquim](https://yyz1.discourse-cdn.com/flex047/user_avatar/forum.generic-mapping-tools.org/joaquim/32/16_2.png) [@Joaquim](https://forum.generic-mapping-tools.org/u/Joaquim)\
**Post date:** [April 29, 2021, 1:08pm UTC](https://forum.generic-mapping-tools.org/t/error-caught-signal-number-11-segmentation-fault-at-lib-x86-64-linux-gnu-libc-so-6-0xb1426-0x7f576c0c1426-0x4/1613/4 "2021-04-29T13:08:55Z")

</div>

Yomi,

We need more than that. We need a little WORKING example that reproduces the error.Can you isolate one file where the crash occurs and make it available to us?

---

<div class="post-metadata">

**Author:** ![Joleonar](https://avatars.discourse-cdn.com/v4/letter/j/ed8c4c/32.png) [@Joleonar](https://forum.generic-mapping-tools.org/u/Joleonar)\
**Post date:** [September 27, 2025, 4:10pm UTC](https://forum.generic-mapping-tools.org/t/error-caught-signal-number-11-segmentation-fault-at-lib-x86-64-linux-gnu-libc-so-6-0xb1426-0x7f576c0c1426-0x4/1613/5 "2025-09-27T16:10:49Z")

</div>

Hi @yomiagus, I had the same problem. I was able to fix it by just deleting the first row of the file, which contained the column names

---

<div class="post-metadata">

**Author:** ![Joaquim](https://yyz1.discourse-cdn.com/flex047/user_avatar/forum.generic-mapping-tools.org/joaquim/32/16_2.png) [@Joaquim](https://forum.generic-mapping-tools.org/u/Joaquim)\
**Post date:** [September 27, 2025, 7:49pm UTC](https://forum.generic-mapping-tools.org/t/error-caught-signal-number-11-segmentation-fault-at-lib-x86-64-linux-gnu-libc-so-6-0xb1426-0x7f576c0c1426-0x4/1613/6 "2025-09-27T19:49:49Z")

</div>

Of you real want to help, instead of reviving and old thread with a low info post, you should show us a full working example where **not removing a header line in file leads to a crash**

---

<div class="post-metadata">

**Author:** ![Joleonar](https://avatars.discourse-cdn.com/v4/letter/j/ed8c4c/32.png) [@Joleonar](https://forum.generic-mapping-tools.org/u/Joleonar)\
**Post date:** [September 27, 2025, 9:27pm UTC](https://forum.generic-mapping-tools.org/t/error-caught-signal-number-11-segmentation-fault-at-lib-x86-64-linux-gnu-libc-so-6-0xb1426-0x7f576c0c1426-0x4/1613/7 "2025-09-27T21:27:33Z")

</div>

Excuse me, I had the same problem today and I stumbled upon this post where **you didn’t know the answer**. I just wanted to help based on solution I found

Here the “full working example”

**The file called menegrande.txt with header**

| year | month | day | hour | minute | sec | rloc | lat | lon | depth | age | nsta | rms | mag |
| --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- |
| 2025 | 9 | 4 | 01 | 42 | 31.5 | L | 9.474 | -69.798 | 14.4 | FUN | 3 | 0.4 | 2.3 |
| 2025 | 9 | 4 | 03 | 22 | 32.0 | L | 8.885 | -70.759 | 12.0 | FUN | 5 | 0.1 | 3.6 |
| 2025 | 9 | 4 | 03 | 22 | 33.5 | L | 8.915 | -70.579 | 4.2 | FUN | 7 | 0.2 | 3.6 |

**The comand line**  
gawk ‘{print $9, $8, $10}’ sismos\_menegrande.txt | project -C$center -A$azimuth -Fxyzpqrs -W$width -L$length -V \> vigia\_07\_13.tmp

**Output Error**  
ERROR: Caught signal number 11 (Segmentation fault) at  
/usr/local/lib/libgmt.so.6(GMT\_project+0x1625)[0x7fb3056b8da5]  
[0x0]  
Stack backtrace:  
/usr/local/lib/libgmt.so.6(sig\_handler+0x2b1)[0x7fb30549b5e1]  
/lib/x86\_64-linux-gnu/libpthread.so.0(+0x12980)[0x7fb305255980]  
/usr/local/lib/libgmt.so.6(GMT\_project+0x1625)[0x7fb3056b8da5]  
/usr/local/lib/libgmt.so.6(GMT\_Call\_Module+0xc6)[0x7fb3054b0ee6]  
project(main+0x5fb)[0x557cd11f331b]  
/lib/x86\_64-linux-gnu/libc.so.6(\_\_libc\_start\_main+0xe7)[0x7fb304e73c87]  
project(\_start+0x2a)[0x557cd11f383a]

**The file without header**

| 2025 | 9 | 4 | 01 | 42 | 31.5 | L | 9.474 | -69.798 | 14.4 | FUN | 3 | 0.4 | 2.3 |
| --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- |
| 2025 | 9 | 4 | 03 | 22 | 32.0 | L | 8.885 | -70.759 | 12.0 | FUN | 5 | 0.1 | 3.6 |
| 2025 | 9 | 4 | 03 | 22 | 33.5 | L | 8.915 | -70.579 | 4.2 | FUN | 7 | 0.2 | 3.6 |
| 2025 | 9 | 4 | 04 | 26 | 0.6 | L | 8.806 | -70.720 | 13.1 | FUN | 3 | 0.0 | 2.5 |
| 2025 | 9 | 10 | 04 | 01 | 46.9 | L | 10.753 | -70.176 | 23.7 | FUN | 7 | 0.3 | 2.9 |
| 2025 | 9 | 12 | 10 | 48 | 15.3 | L | 8.741 | -70.693 | 17.1 | FUN | 3 | 0.1 | 2.6 |
| 2025 | 9 | 12 | 23 | 41 | 56.3 | L | 9.954 | -69.923 | 5.0 | FUN | 4 | 0.2 | 2.4 |

**The same line command**  
gawk ‘{print $9, $8, $10}’ sismos\_menegrande.txt | project -C$center -A$azimuth -Fxyzpqrs -W$width -L$length -V \> vigia\_07\_13.tmp

**The output**

| -69.798 | 9.474 | 14.4 | 0.676049569917 | -0.793767339609 | -70.2584552956 | 10.1253002273 |
| --- | --- | --- | --- | --- | --- | --- |
| -70.759 | 8.885 | 12 | -0.439101742016 | -0.733861358776 | -71.1856765679 | 9.48594962625 |
| -70.579 | 8.915 | 4.2 | -0.276177539231 | -0.811224324566 | -71.0504303937 | 9.57951486924 |
| -70.72 | 8.806 | 13.1 | -0.452833224618 | -0.820680229037 | -71.1970719243 | 9.47806143748 |
| -70.693 | 8.741 | 17.1 | -0.468241175017 | -0.889234497086 | -71.2098579087 | 9.46920974664 |
| -69.923 | 9.954 | 5 | 0.849105560726 | -0.329402476317 | -70.1142382042 | 10.2242893644 |

Thank you for your time

---

<div class="post-metadata">

**Author:** ![Joaquim](https://yyz1.discourse-cdn.com/flex047/user_avatar/forum.generic-mapping-tools.org/joaquim/32/16_2.png) [@Joaquim](https://forum.generic-mapping-tools.org/u/Joaquim)\
**Post date:** [September 27, 2025, 10:04pm UTC](https://forum.generic-mapping-tools.org/t/error-caught-signal-number-11-segmentation-fault-at-lib-x86-64-linux-gnu-libc-so-6-0xb1426-0x7f576c0c1426-0x4/1613/8 "2025-09-27T22:04:41Z")

</div>

> [@Joleonar](#):
>
> Here the “full working example”

Sorry, but it isn’t.

- No file, just a printed table.
- No idea what those are ` -C$center -A$azimuth -Fxyzpqrs -W$width -L$length`

And frankly, I’ll better stop answering to posts in unix.

---

<div class="post-metadata">

**Author:** ![Joleonar](https://avatars.discourse-cdn.com/v4/letter/j/ed8c4c/32.png) [@Joleonar](https://forum.generic-mapping-tools.org/u/Joleonar)\
**Post date:** [September 27, 2025, 10:14pm UTC](https://forum.generic-mapping-tools.org/t/error-caught-signal-number-11-segmentation-fault-at-lib-x86-64-linux-gnu-libc-so-6-0xb1426-0x7f576c0c1426-0x4/1613/9 "2025-09-27T22:14:34Z")

</div>

Actually, I think you didn’t understand anything

---

<div class="post-metadata">

**Author:** ![Joaquim](https://yyz1.discourse-cdn.com/flex047/user_avatar/forum.generic-mapping-tools.org/joaquim/32/16_2.png) [@Joaquim](https://forum.generic-mapping-tools.org/u/Joaquim)\
**Post date:** [September 27, 2025, 11:11pm UTC](https://forum.generic-mapping-tools.org/t/error-caught-signal-number-11-segmentation-fault-at-lib-x86-64-linux-gnu-libc-so-6-0xb1426-0x7f576c0c1426-0x4/1613/10 "2025-09-27T23:11:41Z")

</div>

Yes.

---

<div class="post-metadata">

**Author:** ![mkononets](https://yyz1.discourse-cdn.com/flex047/user_avatar/forum.generic-mapping-tools.org/mkononets/32/4029_2.png) [@mkononets](https://forum.generic-mapping-tools.org/u/mkononets)\
**Post date:** [September 28, 2025, 11:12am UTC](https://forum.generic-mapping-tools.org/t/error-caught-signal-number-11-segmentation-fault-at-lib-x86-64-linux-gnu-libc-so-6-0xb1426-0x7f576c0c1426-0x4/1613/11 "2025-09-28T11:12:48Z")

</div>

Ok as there might be an issue. Technically you are expected to do approximately the following:

1. save example data to a separate file like below. If it is actually the header line that causes the crash, first 10 lines should be more than enough:

```auto
gawk '{print $9, $8, $10}' sismos_menegrande.txt | head > data.txt

```

1. print out your `project` call from the original script - with all the script variables substituted by the values, something like below (output redirection does not matter):

```auto
echo "project -C$center -A$azimuth -Fxyzpqrs -W$width -L$length -V"

```

1. if the crash is still there (confirm this by manually running the `project` call on `data.txt`): post `data.txt` and the crashing `project` call here. You can attach a file by drag-and-dropping it into the post editing window.
2. maybe a short apology to @Joaquim, cause it’s him who’s gonna be checking and fixing the codes in case there’s an issue.
