wefalk / geanypdb

Automatically exported from code.google.com/p/geanypdb
GNU General Public License v2.0
0 stars 0 forks source link

crashes with geany 0.20 #1

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Download geany 0.20 source and install
2. build and install geanypdb
3. cp src/geanypdb.so  ~/.config/geany/plugins/
4. Start geany
5. Enably geanypdb plugin in plugin menu
6. open pyton file
7. choose debug -> run with PDB

What is the expected output? What do you see instead?
Crashes...
geany: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.0.
geany: ../../src/xcb_io.c:249: process_responses: Assertion `(((long) 
(dpy->last_request_read) - (long) (dpy->request)) <= 0)' failed.

What version of the product are you using? On what operating system?
Revision 10
geany 0.20
Ubuntu 10 LTS

Please provide any additional information below.
Sorry have not tried to get a core dump yet.

Original issue reported on code.google.com by Mathew.B...@gmail.com on 10 Jun 2011 at 4:46

GoogleCodeExporter commented 9 years ago
Same here...

Original comment by tiago...@gmail.com on 1 Aug 2011 at 1:39

GoogleCodeExporter commented 9 years ago
Same here, Geany 0.21 on ArchLinux

Original comment by eshiz...@gmail.com on 14 Dec 2011 at 8:11

GoogleCodeExporter commented 9 years ago
I have found several bugs:

You have typos in debugger.py ("). Besides the two first lines are inverted, 
you must put ALWAYS #!/usr/bin/env python (no quotes) BEFORE # -*- coding: 
utf-8 -*-

You are calling gnome-terminal in terminal.sh and this program is not installed 
in all distros. You must use a generic terminal call

There are no /usr/lib/geany path. Best chances are copying the .so to 
~/.config/geany/plugins (no sudo required!)

You are not copying debuger.py and terminal.sh to a folder with the .so, so it 
cannot find them.

terminal.sh does not have exec permission, so it cannot run

When all this issues are corrected you can reach to inside terminal.sh

I didn't check ths C files, but you have bugs in the sh and py files. 

Original comment by david.aponte on 7 Nov 2014 at 6:59