[Geany-Users] Segmentation Fault
Chris Spencer
chrisspen at xxxxx
Mon May 22 16:58:19 UTC 2017
Here's another detail I just discovered. This only happens when I launch
Geany from inside an activated Python virtual environment. If I first
deactivate the virtualenv, so Geany uses the global Python installation,
then it launches without error.
On Mon, May 22, 2017 at 12:51 PM, Chris Spencer <chrisspen at gmail.com> wrote:
> I've run into another segmentation fault again.
>
> Here's my backtrace and gdb output:
>
> @localhost:$ gdb geany
> GNU gdb (Ubuntu 7.11.1-0ubuntu1~16.04) 7.11.1
> Copyright (C) 2016 Free Software Foundation, Inc.
> License GPLv3+: GNU GPL version 3 or later <
> http://gnu.org/licenses/gpl.html>
> This is free software: you are free to change and redistribute it.
> There is NO WARRANTY, to the extent permitted by law. Type "show
> copying"
> and "show warranty" for details.
> This GDB was configured as "x86_64-linux-gnu".
> Type "show configuration" for configuration details.
> For bug reporting instructions, please see:
> <http://www.gnu.org/software/gdb/bugs/>.
> Find the GDB manual and other documentation resources online at:
> <http://www.gnu.org/software/gdb/documentation/>.
> For help, type "help".
> Type "apropos word" to search for commands related to "word"...
> Reading symbols from geany...(no debugging symbols found)...done.
> (gdb) run -i project.geany
> Starting program: /usr/bin/geany -i project.geany
> [Thread debugging using libthread_db enabled]
> Using host libthread_db library "/lib/x86_64-linux-gnu/
> libthread_db.so.1".
> [New Thread 0x7fffed913700 (LWP 4060)]
> [New Thread 0x7fffed112700 (LWP 4061)]
> [New Thread 0x7fffec911700 (LWP 4062)]
> [New Thread 0x7fffdf720700 (LWP 4063)]
> [New Thread 0x7fffdef1f700 (LWP 4064)]
>
> Thread 1 "geany" received signal SIGSEGV, Segmentation fault.
> 0x00007fffdcb37801 in PyModule_AddObject () from
> /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0
> (gdb) bt
> #0 0x00007fffdcb37801 in PyModule_AddObject () from
> /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0
> #1 0x00007fffdcf92c20 in ?? () from /usr/lib/x86_64-linux-gnu/
> geany/geanypy.so
> #2 0x00007ffff79a5e2d in ?? () from /usr/lib/x86_64-linux-gnu/
> libgeany.so.0
> #3 0x00007ffff79a7621 in ?? () from /usr/lib/x86_64-linux-gnu/
> libgeany.so.0
> #4 0x00007ffff79a03d5 in main_lib () from /usr/lib/x86_64-linux-gnu/
> libgeany.so.0
> #5 0x00007ffff7368830 in __libc_start_main (main=0x4005a0, argc=3,
> argv=0x7fffffffd9f8, init=<optimized out>, fini=<optimized out>,
> rtld_fini=<optimized out>, stack_end=0x7fffffffd9e8) at
> ../csu/libc-start.c:291
> #6 0x00000000004005d9 in ?? ()
>
> How do I fix this?
>
> My project's primarily a Python project, and if I'm reading the backtrace
> properly, it's involving Python. I don't remember enabling any
> Python-specific Geany plugins, so I'm not sure why it's running Python, but
> even so, why is Python causing Geany to crash upon startup? I have many
> other Geany Python projects that open without issue.
>
> My Geany version is:
>
> geany 1.30.1 (built on 2017-03-21 with GTK 2.24.30, GLib 2.48.2)
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.geany.org/pipermail/users/attachments/20170522/a77de6ca/attachment.html>
More information about the Users
mailing list