Dragon crash......
12 Nov 2021 23:16 #226252
by Roguish
Dragon crash...... was created by Roguish
I'm working on using qtdragon. slightly modified to fit my screen, and added a few hal pin displays. nothing to wild.
well, using it today. CRASH, twice. same thing.
Segmentation faults.
see the pics.
Loaded a simple, short file. Edited it an external editor (pluma). Touched the 'reload' button, and wam. crash.
did this twice.
not sure what's up...........
any clues.??????
well, using it today. CRASH, twice. same thing.
Segmentation faults.
see the pics.
Loaded a simple, short file. Edited it an external editor (pluma). Touched the 'reload' button, and wam. crash.
did this twice.
not sure what's up...........
any clues.??????
Please Log in or Create an account to join the conversation.
13 Nov 2021 00:29 #226258
by cmorley
Replied by cmorley on topic Dragon crash......
I wonder if it's because your filename uses spaces?
Or try a different external editor ( adds bad line endings?)
Otherwise there is not enough info to draw any more troubleshooting idea.
Chris
Or try a different external editor ( adds bad line endings?)
Otherwise there is not enough info to draw any more troubleshooting idea.
Chris
The following user(s) said Thank You: Roguish
Please Log in or Create an account to join the conversation.
13 Nov 2021 02:35 - 13 Nov 2021 02:35 #226266
by phillc54
Replied by phillc54 on topic Dragon crash......
I have noticed the same in QtPlasmaC on GUI shutdown with python 3.9
forum.linuxcnc.org/plasmac/43880-qtplasm...ntation-fault#226178
forum.linuxcnc.org/plasmac/43880-qtplasm...ntation-fault#226178
Last edit: 13 Nov 2021 02:35 by phillc54.
The following user(s) said Thank You: Roguish
Please Log in or Create an account to join the conversation.
13 Nov 2021 15:27 #226325
by Roguish
Replied by Roguish on topic Dragon crash......
cmorley,
thanks for the quick look over.
what additional info is needed?
also, a seg fault has always been pretty serious to me.... usually causes a BSD.
and seriously, spaces in a file name as a cause? thought that went away back in the '90s.
I've been using pluma for a couple of years and never had an issue with axis. before that it was gedit, which is unfortunately pretty much gone.
I think i'll try the linux install of notepad++ (yeah, it exists)
by the way, my velocity and ferror display works fine.....thanks.
thanks for the quick look over.
what additional info is needed?
also, a seg fault has always been pretty serious to me.... usually causes a BSD.
and seriously, spaces in a file name as a cause? thought that went away back in the '90s.
I've been using pluma for a couple of years and never had an issue with axis. before that it was gedit, which is unfortunately pretty much gone.
I think i'll try the linux install of notepad++ (yeah, it exists)
by the way, my velocity and ferror display works fine.....thanks.
Please Log in or Create an account to join the conversation.
14 Nov 2021 12:50 #226459
by cmorley
Replied by cmorley on topic Dragon crash......
you could run qtvcp with the -d or -v switches for more degug detail.
Toy could try to find someway to make the error consistant and repeatable.
ie a particular program loaded does it - then upload that program.
You could try my suggestion about spaces in the file because it's easy to test.
You could see if it crashes on the sim config too.
If you have been using pluma for a while then it's probably not that.
If the problem is intermittent then it's the hardest type to fix.
Chris
Toy could try to find someway to make the error consistant and repeatable.
ie a particular program loaded does it - then upload that program.
You could try my suggestion about spaces in the file because it's easy to test.
You could see if it crashes on the sim config too.
If you have been using pluma for a while then it's probably not that.
If the problem is intermittent then it's the hardest type to fix.
Chris
Please Log in or Create an account to join the conversation.
15 Nov 2021 02:27 - 15 Nov 2021 02:28 #226528
by phillc54
Replied by phillc54 on topic Dragon crash......
Following are what I see with python3.9, there are no issues with python 3.7
This is the terminal messages during shutdown using -d:
[QTvcp.QTVCP.QT_MAKEGUI][DEBUG] Calling handler file Closing_cleanup__ function. (qt_makegui.py:126)
[QTvcp.QTVCP.QT_MAKEPINS][DEBUG] Saving Main Window geometry to preference file. (qt_makepins.py:111)
[QTvcp.QTVCP.QT_MAKEPINS][DEBUG] calling widget's _hal_cleanup functions (qt_makepins.py:92)
[QTvcp.QTVCP.WIDGETS.GCODE_GRAPHICS][DEBUG] Saving conv_preview data to file. (gcode_graphics.py:212)
[QTvcp.QTVCP.WIDGETS.ORIGIN_OFFSETVIEW][DEBUG] Saving originoffsetview data to file. (origin_offsetview.py:102)
[QTvcp.QTVCP.WIDGETS.GCODE_GRAPHICS][DEBUG] Saving gcodegraphics data to file. (gcode_graphics.py:212)
/home/phill/linuxcnc-dev/scripts/linuxcnc: line 930: 5103 Segmentation fault $EMCDISPLAY -ini "$INIFILE" $EMCDISPLAYARGS $EXTRA_ARGS
Shutting down and cleaning up LinuxCNC...
task: 974 cycles, min=0.000006, max=0.014158, avg=0.009831, 0 latency excursions (> 10x expected cycle time of 0.010000s)
Note: Using POSIX realtime
LinuxCNC terminated with an error. You can find more information in the log:
/home/phill/linuxcnc_debug.txt
and
/home/phill/linuxcnc_print.txt
as well as in the output of the shell command 'dmesg' and in the terminal
Using -d gives the following error on startup:
Traceback (most recent call last):
File "/home/phill/linuxcnc-dev/bin/qtvcp", line 428, in <module>
APP = QTVCP()
File "/home/phill/linuxcnc-dev/bin/qtvcp", line 249, in __init__
self.panel = qt_makepins.QTPanel(self.hal, PATH, window, opts.debug)
File "/home/phill/linuxcnc-dev/lib/python/qtvcp/qt_makepins.py", line 84, in __init__
LOG.verbose('HAL-ified instance found: {}'.format(idname))
File "/home/phill/linuxcnc-dev/lib/python/qtvcp/logger.py", line 36, in verbose
self._log('VERBOSE', message, args, **kws)
File "/usr/lib/python3.9/logging/__init__.py", line 1585, in _log
self.handle(record)
File "/usr/lib/python3.9/logging/__init__.py", line 1595, in handle
self.callHandlers(record)
File "/usr/lib/python3.9/logging/__init__.py", line 1656, in callHandlers
if record.levelno >= hdlr.level:
TypeError: '>=' not supported between instances of 'str' and 'int'
This is the terminal messages during shutdown using -d:
Warning: Spoiler!
[QTvcp.QTVCP.QT_MAKEGUI][DEBUG] Calling handler file Closing_cleanup__ function. (qt_makegui.py:126)
[QTvcp.QTVCP.QT_MAKEPINS][DEBUG] Saving Main Window geometry to preference file. (qt_makepins.py:111)
[QTvcp.QTVCP.QT_MAKEPINS][DEBUG] calling widget's _hal_cleanup functions (qt_makepins.py:92)
[QTvcp.QTVCP.WIDGETS.GCODE_GRAPHICS][DEBUG] Saving conv_preview data to file. (gcode_graphics.py:212)
[QTvcp.QTVCP.WIDGETS.ORIGIN_OFFSETVIEW][DEBUG] Saving originoffsetview data to file. (origin_offsetview.py:102)
[QTvcp.QTVCP.WIDGETS.GCODE_GRAPHICS][DEBUG] Saving gcodegraphics data to file. (gcode_graphics.py:212)
/home/phill/linuxcnc-dev/scripts/linuxcnc: line 930: 5103 Segmentation fault $EMCDISPLAY -ini "$INIFILE" $EMCDISPLAYARGS $EXTRA_ARGS
Shutting down and cleaning up LinuxCNC...
task: 974 cycles, min=0.000006, max=0.014158, avg=0.009831, 0 latency excursions (> 10x expected cycle time of 0.010000s)
Note: Using POSIX realtime
LinuxCNC terminated with an error. You can find more information in the log:
/home/phill/linuxcnc_debug.txt
and
/home/phill/linuxcnc_print.txt
as well as in the output of the shell command 'dmesg' and in the terminal
Using -d gives the following error on startup:
Warning: Spoiler!
Traceback (most recent call last):
File "/home/phill/linuxcnc-dev/bin/qtvcp", line 428, in <module>
APP = QTVCP()
File "/home/phill/linuxcnc-dev/bin/qtvcp", line 249, in __init__
self.panel = qt_makepins.QTPanel(self.hal, PATH, window, opts.debug)
File "/home/phill/linuxcnc-dev/lib/python/qtvcp/qt_makepins.py", line 84, in __init__
LOG.verbose('HAL-ified instance found: {}'.format(idname))
File "/home/phill/linuxcnc-dev/lib/python/qtvcp/logger.py", line 36, in verbose
self._log('VERBOSE', message, args, **kws)
File "/usr/lib/python3.9/logging/__init__.py", line 1585, in _log
self.handle(record)
File "/usr/lib/python3.9/logging/__init__.py", line 1595, in handle
self.callHandlers(record)
File "/usr/lib/python3.9/logging/__init__.py", line 1656, in callHandlers
if record.levelno >= hdlr.level:
TypeError: '>=' not supported between instances of 'str' and 'int'
Last edit: 15 Nov 2021 02:28 by phillc54. Reason: Paste the correct error messages.
Please Log in or Create an account to join the conversation.
15 Nov 2021 03:19 #226533
by phillc54
Replied by phillc54 on topic Dragon crash......
It looks to be above my paygrade, it is happening somewhere between:
qtvcp.py Line #384 sys.exit(0)
and:
linuxcnc.in Line #958 result=$?
qtvcp.py Line #384 sys.exit(0)
and:
linuxcnc.in Line #958 result=$?
Please Log in or Create an account to join the conversation.
15 Nov 2021 03:20 #226534
by cmorley
Replied by cmorley on topic Dragon crash......
The shutdown error and what Roguish is describing is most likely different problems.
And looks like python3 has broken verbose logging..
And looks like python3 has broken verbose logging..
The following user(s) said Thank You: Roguish
Please Log in or Create an account to join the conversation.
15 Nov 2021 03:23 #226535
by phillc54
Replied by phillc54 on topic Dragon crash......
Aha, I saw the seg fault and assumed...The shutdown error and what Roguish is describing is most likely different problems.
The fun never ends.And looks like python3 has broken verbose logging..
Please Log in or Create an account to join the conversation.
15 Nov 2021 16:32 #226587
by Roguish
Replied by Roguish on topic Dragon crash......
Not sure which python version I'm on. 3.7 I think. I will check. if 3.7 I will use the -d option and keep a close eye for errors.
The crash error I described earlier is easy to spot, as the whole screen/code just flashes away......
The crash error I described earlier is easy to spot, as the whole screen/code just flashes away......
Please Log in or Create an account to join the conversation.
Moderators: cmorley
Time to create page: 0.136 seconds