Bug 76742 - no way to abort any tool in CDT
Summary: no way to abort any tool in CDT
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Developer Suite
Classification: Retired
Component: CDT (Show other bugs)
(Show other bugs)
Version: 1.0
Hardware: All Linux
medium
medium
Target Milestone: ---
Assignee: eclipse-bugs
QA Contact: eclipse-bugs
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2002-10-25 17:29 UTC by Keith Seitz
Modified: 2007-04-18 16:47 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2004-08-03 21:29:31 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

Description Keith Seitz 2002-10-25 17:29:46 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20021003

Description of problem:
If I run any kind of tool in the CDT (build/make or external build tool like
configure), it cannot be aborted. It must complete. This is especially painful
if one forgets to select the "stop on error" option of the build preferences for
a project.

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. create external build tool to run configure (for example)
2. run this tool.
3. before it finishes, click "cancel"... The button is disabled, but nothing
really happens until the tool finishes executing.

Do the same for building a project.

Actual Results:  It just keeps on going and going and going.

Expected Results:  Should have stopped.

Additional info:

Comment 1 Jeremy Handcock 2003-11-19 22:13:32 UTC
See upstream bug https://bugs.eclipse.org/bugs/show_bug.cgi?id=41752

This is an eclipse platform issue rather than a CDT one.  I'll move
the upstream PR to the proper eclipse.org component.

Comment 2 Keith Seitz 2004-08-03 21:29:31 UTC
Well, this, too, seems to be rectified with the Eclipse 3.0/CDT 2.0
release. Yeah!


Note You need to log in before you can comment on or make changes to this bug.