@johnbester: do you see a chance to re-produce the problem? It's quite old and
we are now on geany-plugins 1.35. Or do you think we should close it?
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
Thanks for looking into the problem. I can't however remember exactly why I
logged this bug and whether or not I used a different editor (such as GEdit)
for some time. I am currently using Geany 1.27 on Ubuntu 16.04 and I am not
aware of any pressing issues at this time. At the time of this bug
Unfortunately you don't seem to have debugging symbols for the plugin so it
doesn't tell where the problem is.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
Can you re-rerun Geany passing `--g-fatal-warnings` argument and post this
backtrace?
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany-plugins/issues/309#issuecomment-368277173
@Top-Dog did you actually mean version 1.23 ?
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany-plugins/issues/309#issuecomment-368277116
Hop this helps. I'm running geany via Bash on Win10 using Xming Server, so I
could only attach to the running process. Might need to rebuild geany with -g
flag?
> (gdb) continue
> Continuing.
>
> Program received signal SIGSEGV, Segmentation fault.
> __strchr_sse2 () at
Would be useful if someone could [provide a
backtrace](https://www.geany.org/Support/Bugs) since it will show where the
crash happens.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
