Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 311215 - NullPointerException in CVSFileHistoryProvider
Summary: NullPointerException in CVSFileHistoryProvider
Status: CLOSED WONTFIX
Alias: None
Product: Platform
Classification: Eclipse Project
Component: CVS (show other bugs)
Version: 4.0   Edit
Hardware: PC Windows Vista
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: platform-cvs-inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2010-04-30 13:09 EDT by Brian Wilkerson CLA
Modified: 2022-02-23 03:33 EST (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Brian Wilkerson CLA 2010-04-30 13:09:35 EDT
Build Identifier: M20090917-0800

I work for Instantiations, and one of our customers reported a bug. Their log file contained a stack trace that started with:

!STACK 0
java.lang.NullPointerException
	at org.eclipse.team.internal.ccvs.core.filehistory.CVSFileHistory.refresh(CVSFileHistory.java:138)
	at org.eclipse.team.internal.ccvs.core.filehistory.CVSFileHistoryProvider.getFileHistoryFor(CVSFileHistoryProvider.java:42)

Looking at the method in question, it is clear that either tags[j] or tempTag is null. Given that tempTag is assigned a value on line 133 and that the Javadoc for getTag() explicitly states that null is a valid return value, I think that refresh needs to check for null.

Reproducible: Didn't try
Comment 1 Eclipse Webmaster CLA 2019-09-06 16:10:43 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.
Comment 2 Eclipse Genie CLA 2022-02-23 03:33:18 EST
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. As such, we're closing this bug.

If you have further information on the current state of the bug, please add it and reopen this bug. 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.