Bug 27840 - segfault when using BufferedImage.TYPE_3BYTE_BGR
Summary: segfault when using BufferedImage.TYPE_3BYTE_BGR
Status: RESOLVED FIXED
Alias: None
Product: classpath
Classification: Unclassified
Component: awt (show other bugs)
Version: 0.92
: P3 normal
Target Milestone: ---
Assignee: Not yet assigned to anyone
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-05-31 13:07 UTC by Norman Hendrich
Modified: 2006-12-01 15:53 UTC (History)
1 user (show)

See Also:
Host:
Target:
Build:
Known to work:
Known to fail:
Last reconfirmed:

Attachments
testcase to trigger the segfault. (3.30 KB, text/plain)
2006-05-31 13:13 UTC, Norman Hendrich 		Details
View All 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 Norman Hendrich 2006-05-31 13:07:48 UTC 
Trying to use a BufferedImage.TYPE_3BYTE_BGR (or TYPE_4BYTE_BGR or TYPE_INT_BGR
as a synonym for TYPE_3BYTE_BGR) segfaults on classpath cvs 2006.05.31. See attached testcase.

I tried running jamvm under gdb, but I get no meaningful stacktrace. Also, the
partially created window remains on screen, even after jamvm has terminated:

jamvm PRuui
PRuui selftest and demo...

paint'ing: 
getShadeImage: 39
Segmentation fault
Comment 1 Norman Hendrich 2006-05-31 13:13:46 UTC 
Created attachment 11553 [details]
testcase to trigger the segfault.

Edit the source to try TYPE_INT_BGR, TYPE_3BYTE_BGR, and TYPE_4BYTE_BGR
for instant segfaults. Using TYPE_INT_RGB works initially on my system,
but crashes after a few iterations of the outer loop.
Comment 2 Francis Kung 2006-12-01 15:53:08 UTC 
No longer segfaults, seems to have been fixed some time in the past months