On Wed, Jun 19, 2019 at 10:08 PM Chris George <[email protected]> wrote:
>
> setting leoID from os.getenv('USER'): 'chris'
> Leo 6.0-b1, master branch, build 445dfa149e
> 2019-06-18 09:45:56 -0500
> KCrash: crashing... crashRecursionCounter = 2
>
> The exact same crash on starting Leo.
>
I would have been shocked if that were not true.
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.
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.
You should be able to find the culprit pretty easily. This is, after all,
a repeatable bug. Are you game?
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
--
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/CAMF8tS12usS%3DngJ_f3MUsA7dzhWQ5MYxoJWsEPdwMLD_vke84Q%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
