crashes on auto-complete (Ctrl - K) on ubuntu

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Open a Python Source File
2a. Type "gtk." on anywhere 
   or 
2b. Type "self." in a class body and press Ctrl+k

What is the expected output? What do you see instead?

Open list box for available elements. Or at least don't crash. It crashes
without warning or saving. Reports a segmentation fault.

IMPORTANT!!! Please answer these questions for any and ALL bug reports

What version of the product are you using? On what operating system?

0.3.15 from Ubuntu Repository and 0.4.28 downloaded from editra web site.
Both on Ubuntu Intrepid Ibex.

Please find the attached Python Source File which causes the crash and
Editra -d outputs of crashes.

Original issue reported on code.google.com by memede...@gmail.com on 26 Dec 2008 at 3:25

Attachments:

• editra_log_gtk.txt
• editra_log_self.txt
• toDoListEditra.py

[GoogleCodeExporter]

Hello,

I cannot reproduce this. I tried your sample file and the completions come up 
just
fine on my machine without error. (Ubuntu 8.04, python 2.5, wxPython2.8.7.1, 
Editra
0.4.28).

Ctrl+K is for the keyword helper it shows a list of language keywords. If you 
want to
bring up the autocomp list do Ctrl+Space.

There are no errors in your attached log output either. What version of
python/wxPython are you using? (Help=>About...).

Thanks,

Cody

Original comment by CodyPrec...@gmail.com on 26 Dec 2008 at 3:54

• Changed state: Pending

[GoogleCodeExporter]

Really sorry for the false alarm and the lack of logging. About false alarm, I
ignored the start all over routine of computers. Here is what happened: 

After reporting the issue, i removed wxtools and wxgtk2.8 packages from Ubuntu
Intrepid. Thus Editra is removed too. After your comment i reinstalled the 
0.4.28
version of Editra from source which is obtained from editra web site.

When i start the application, gtk auto complete, unlike previously mentioned,  
did
NOT crash the EditRa. But when i try to invoke auto-complete on "self.", it did 
not
open any list. Please find the attached debug info. This time i copied it from 
the
console. So you may find GTK warnings. The error (the [err] part) is same with
previous one. But this time it didn't raise segmentation fault. From user 
perspective
it simply did not respond to auto completion.

By the way: Help -> About:

Platform Info: (linux2, python 2.5.2,wxGTK 2.8.8.0, unicode, gtk2, 
wx-assertions-off,
SWIG-1.3.29)
License: wxWindows (see COPYING.txt for full license)

I just discovered the EditRa and kind o' loved it. It seems very user-oriented 
and
compact also the vi mode is great. So i want to use it. Thank you for your 
time. I
can supply additional info if it's needed.

Original comment by memede...@gmail.com on 26 Dec 2008 at 9:56

Attachments:

• editra_log_new.txt

[GoogleCodeExporter]

Hello,

The Gtk Warnings are annoying but harmless. I think they are coming from 
wxPython 
somewhere but haven't been able to find them yet.

The current autocompletion is not perfect (mostly just a proof of concept I 
wrote to 
help me with development) so sometimes it cannot provide completion tips due to 
imperfections in the parser, it does pretty well most the time but sometimes 
gets 
stuck. The log output from the pycomp module shows it ran into some trouble 
while 
parsing and reformatting your code for introspection. This can be caused by a 
few different causes, 1) the parser just made a mistake, 2) you have syntax 
errors in 
your code, etc... I plan to enhance the autocompletion in future releases but 
have 
other priorities right now.

Since there is no crash or issue I am going to close this as Invalid. Let me 
know if 
you have any further issues.

Cody

Original comment by CodyPrec...@gmail.com on 26 Dec 2008 at 3:11

• Changed state: Invalid

[GoogleCodeExporter]

Hmm auto-completion related issues just made editRa un-usable for me. I'm 
starting to
get segfaults again. This time i was importing an other python file from the 
same
directory. And use it like:

import asd
.....
def __init__():
....
   asd.

after typing . (dot) application immediately crashes with segmentation fault. I 
tried
many times and even delete the $home/.EditRa directory but still no luck. So i 
give
up for now.

I attach the debug information which is copied from console. Maybe my installed
libraries don't compatible with the application. 

One last thing: After I had closed the auto-completion from menu, EditRa didn't
crash. So i guess it's about auto-completion. Thank you again for your interest.

Original comment by memede...@gmail.com on 27 Dec 2008 at 12:38

Attachments:

• editRa.log

[GoogleCodeExporter]

Not sure what to tell you. As I cannot reproduce this issue at all on any of my
installations nor have I ever seen it happen in the past.

Is your computer 64 bit or 32 bit? I have seen some other unexplained issues on 
64
bit machines in the past in reports from users.

The configuration data in ~/.Editra has nothing to do with the autocompletion so
deleting it will not affect anything, all the autocompletion stuff is done 
ondemand
in in memory based on the contents of the current buffer. I am not sure why they
would go away after you uninstalled last time and came back again, sounds like
something else may be going on somewhere.

Though it shouldn't matter, just so you know you don't need to put ';' at the 
end of
the line in python code.

I will keep an eye open for something that could cause this though I am not 
sure what
could.

Thank,

Cody

Original comment by CodyPrec...@gmail.com on 27 Dec 2008 at 3:37

[GoogleCodeExporter]

I suppose you are right, that the problem is specific to my system. I also tried
Stani's Python Editor, which is also using wxWidgets, and it fails to start 
too. I
blame wxWidgets for now. If it's a general problem then i'll let you know. 
Until then
i'll stick with Geany.

About the ';' at the ends, well after more than a decade of coding with c and 
java,
it feels like letters will fall down from rows if i don't put ';' at the ends. 
Sounds
like silly but i become a little irritated if i don't see them. 

Thank you again.

Original comment by memede...@gmail.com on 27 Dec 2008 at 4:32