Bug 262691 - Stack trace still visible when suspended thread resumed (running)
Summary: Stack trace still visible when suspended thread resumed (running)
Status: NEW
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Debug (show other bugs)
Version: 3.4.1   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: JDT-Debug-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2009-01-27 18:29 EST by Ori Kremer CLA
Modified: 2024-05-11 05:26 EDT (History)
1 user (show)

See Also:


Attachments
screenshot (52.58 KB, image/jpeg)
2009-01-27 18:29 EST, Ori Kremer CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Ori Kremer CLA 2009-01-27 18:29:19 EST
Created attachment 123966 [details]
screenshot

Build ID: M20080911-1700

Steps To Reproduce:
Happens when debugging code within a jar with its attached source.
Attached a screen shot of it.

More information:
Comment 1 Darin Wright CLA 2009-01-27 18:49:24 EST
Any exceptions in the log when this happens?
Comment 2 Ori Kremer CLA 2009-01-27 18:55:28 EST
(In reply to comment #1)
> Any exceptions in the log when this happens?
> No exception in the error log.

Comment 3 Darin Wright CLA 2009-06-17 15:24:30 EDT
Any steps to reproduce?
Comment 4 Ori Kremer CLA 2009-06-18 08:57:30 EDT
(In reply to comment #3)
> Any steps to reproduce?
> 

No.
This happened occasionally when debugging code within a jar,
unable to reproduce on demand.
Comment 5 Eclipse Genie CLA 2020-05-29 19:18:08 EDT
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.
Comment 6 Eclipse Genie CLA 2022-05-21 19:56:45 EDT
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.
Comment 7 Eclipse Genie CLA 2024-05-11 05:26:30 EDT
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.