Bug 501300 - Display should be able to startup a JVM to execute arbitrary code
Summary: Display should be able to startup a JVM to execute arbitrary code
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Debug (show other bugs)
Version: 4.6   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Platform-Debug-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-09-13 03:42 EDT by Mickael Istria CLA
Modified: 2016-09-13 03:50 EDT (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Mickael Istria CLA 2016-09-13 03:42:00 EDT 
The Display view could provide a way to execute a piece of Java code even if there's currently no Debug context. Rather than disabling the ability to execute a piece of code, it could start a VM in debug mode, compile the "pad" and allow to execute and inspect it.
Comment 1 Andrey Loskutov CLA 2016-09-13 03:48:45 EDT 
The problem is the classpath, which is given if you have debug context and which is undefined if you want to "Display" something out of the blue. Which JVM should be started? Which projects / libraries should be used? Simply starting a first JVM with empty classpath will lead to many bug reports because no or wrong classes will be found.
Comment 2 Mickael Istria CLA 2016-09-13 03:50:19 EDT 
@Andrey: I agree. In most cases User should be prompted for a classpath to set.