> BTW, can you send a copy of Leo's log pane when you *aren't* crashing.  
> I'm guessing it's some Linux flavor, but I'd like to know the details.
>
>
Leo 6.0-b2-devel, devel branch, build 0e86a7bf76
2019-06-19 21:25:33 -0500
Python 3.6.8, PyQt version 5.12.3
linux

 

> It's time to start thinking about filing a *python* bug report.
>
> Presumably, the segfault happen in the on-create function.  What I would 
> do, if I were you, would be to put a call to g.pdb() here:
>
> def onCreate (tag, keys):
>     '''python_terminal.py onCreate handler.'''
>     c = keys.get('c')
>     if c:
>         g.pdb() 
>         win = MyInterpreter(None,c)
>         c.frame.log.createTab('Python Console',widget=win)
>
> You will very likely take the segfault stepping over the next line.  If 
> so, you can step into that line (the next time), and keep single stepping 
> until you find the line that causes the segfault.
>

Done.
 

>
> You should be able to find the culprit pretty easily.  This is, after all, 
> a repeatable bug.  Are you game?
>

Sure.
 

>
> Once the cause of the segfault is found, we can work on creating a minimal 
> program that demonstrates it, which is what the python devs will want.
>
> Edward
>

 No luck, the process never makes it that far.

chris@technatica:~/leo-editor$ python3 ./launchLeo.py --trace=startup

setting leoID from os.getenv('USER'): 'chris'
reading settings in /home/chris/leo-editor/leo/config/leoSettings.leo
reading settings in /home/chris/.leo/myLeoSettings.leo
reading settings in /home/chris/.leo/themes/BreezeDarkThemeLocal.leo
getGitVersion commit 0e86a7bf76313885be1a75c89367f7ab68869d0e
Author: Edward K. Ream <[email protected]>
Date:   2019-06-19 21:25:33 -0500

    Documented two completed issues

getGitVersion commit 0e86a7bf76313885be1a75c89367f7ab68869d0e
Author: Edward K. Ream <[email protected]>
Date:   2019-06-19 21:25:33 -0500

    Documented two completed issues

Leo 6.0-b2-devel, devel branch, build 0e86a7bf76
2019-06-19 21:25:33 -0500
KCrash: crashing... crashRecursionCounter = 2

This is the exact same crash as before.

FYI, before we started this yesterday I deleted my ~/.leo directory and 
deleted and rebuilt via git my entire Leo installation.

The same behaviour occurs.

This used to trip me up whenever I reinstalled my OS because the plugin was 
enabled by default in LeoSettings.leo.

HTH and awaiting next steps.

 Chris

-- 
You received this message because you are subscribed to the Google Groups 
"leo-editor" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/leo-editor.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/25e0c337-d107-4158-b5e0-69bc35a4974d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to