#1203 closed bug (fixed)
QGIS segfaults when an Action with capture output has an invalid path to executable is called
Reported by: | smizuno | Owned by: | nobody |
---|---|---|---|
Priority: | major: does not work as expected | Milestone: | |
Component: | GUI | Version: | Trunk |
Keywords: | action invalid, capture | Cc: | |
Must Fix for Release: | No | Platform: | All |
Platform Version: | Awaiting user input: | no |
Description
Steps to show the problem:
- create an Action in Layer Properties, specifying a program that doesn't exist - xyz, for example.
- set Capture output (this is due to another bug already reported)
- use Identify on the layer, pick an object
- click on the Action created in step 1
- QGIS quits - segfault
This happens on Windows and Linux; can't test Mac.
Versions at least back to 0.9.0 have this problem.
r8952; Qt 4.3.3 & 4.4.0
Change History (6)
comment:1 by , 16 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
comment:2 by , 15 years ago
Milestone: | Version 1.0.0 → Version 1.0.1 |
---|---|
Resolution: | fixed |
Status: | closed → reopened |
I have this issue with my Windows XP version of QGIS 1.0.0.
According to my "About" dialog, I have: "QGIS version 1.0.0-Kore built against code revision unknown", which I obtained from OSGeo4W yesterday. Sorry, I can't confirm this on any other platform.
comment:3 by , 15 years ago
Note that I only have this crashing behaviour with Capture output enabled.
With Capture output disabled, everything works as expected (including error message if a command is not found).
comment:4 by , 15 years ago
Keywords: | capture added |
---|---|
Milestone: | Version 1.0.2 → Version 1.1.0 |
Summary: | QGIS segfaults when an Action that has an invalid path to executable is called → QGIS segfaults when an Action with capture output has an invalid path to executable is called |
I don't see the other bug that reports the capture output bug (so I modified the summary), but this report is still valid (I have 1.1 - trunk for WinXP via OSGeo4W).
comment:5 by , 15 years ago
Resolution: | → fixed |
---|---|
Status: | reopened → closed |
should be fixed with r10533
Fixed by applying patch in #989.