Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

pscoast -E<valid-code-but-not-DCW> crashes #7484

Open
joa-quim opened this issue May 30, 2023 · 1 comment · Fixed by #7486
Open

pscoast -E<valid-code-but-not-DCW> crashes #7484

joa-quim opened this issue May 30, 2023 · 1 comment · Fixed by #7486
Labels
bug Something isn't working

Comments

@joa-quim
Copy link
Member

This is worst than the example recently brought by Andreas (pscoast -Ejunk). I made this mistake of passing a non DCW code and it crashed.

gmt pscoast -EEUR+p0.5 -REUR -JD28.213/52.993/40.865633333333335/77.24743333333333/15c -Baf -BWSen -P -K > lixo.ps
@joa-quim joa-quim added the bug Something isn't working label May 30, 2023
joa-quim added a commit that referenced this issue Jun 1, 2023
* Do not let go a -E<non-DCW code> and -M or -R. It would crash.

Fixes #7484

* Use strchr instead of strrchr
@joa-quim
Copy link
Member Author

joa-quim commented Jun 6, 2023

#7486 was not good enough.

@joa-quim joa-quim reopened this Jun 6, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant