This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 15751 - Cannot debug with JDK1.1 debuggger implementation
Summary: Cannot debug with JDK1.1 debuggger implementation
Status: CLOSED INVALID
Alias: None
Product: debugger
Classification: Unclassified
Component: Code (show other bugs)
Version: 3.x
Hardware: PC Linux
: P1 blocker (vote)
Assignee: issues@debugger
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2001-09-21 10:53 UTC by Karel Serin
Modified: 2001-10-04 11:29 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
Thrown Exception (1.51 KB, text/plain)
2001-09-21 10:59 UTC, Karel Serin
Details
ide.log (12.62 KB, text/plain)
2001-09-21 11:08 UTC, Karel Serin
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Karel Serin 2001-09-21 10:53:50 UTC
Netbeans build 20010921
=======================

Steps to reproduce:
-------------------
1. Open some app. e.g. MemoryView
2. Go to Properties > Debugger Default Debugging
3. Set Debugger implementation to JDK1.1 debugger implementation
4. Start the debugger 

-Exception java.lang.ArrayIndexOutOfBoundsException is thrown

-Following message appears in the Main window status line
An Exception reached at sun.io.Char.ToByteSingleByte.convert line 154 -
unavailable source file

-The debugging is impossible.
Comment 1 Karel Serin 2001-09-21 10:59:13 UTC
Created attachment 2633 [details]
Thrown Exception
Comment 2 Karel Serin 2001-09-21 11:08:10 UTC
Created attachment 2634 [details]
ide.log
Comment 3 Marian Petras 2001-09-21 14:31:28 UTC
This bug has been reproduced only on Linux.
It was probably caused by an inappropriate 'font.properties' from
official release of JDK 1.3.1 for Linux. See
http://java.sun.com/j2se/1.3/relnotes.html#fontproperties.

The bad behaviour can be fixed by replacing the original
'font.properties' with a newer version of 'font.properties'
(downloadable from the above WWW page).

This bug is not caused by bug in debugger code. The exception that
blocks the debugger's functionality (its stack-trace has been
displayed in the debugger's output window) has been thrown from
constructor of javax.swing.JFrame.
Comment 4 Jan Stola 2001-10-04 11:29:44 UTC
Invalid -> Closed.