Bug 6484 - crash of 16bit subsystem under windows xp professional w. java 1.4 final
Summary: crash of 16bit subsystem under windows xp professional w. java 1.4 final
Status: RESOLVED DUPLICATE of bug 6456
Alias: None
Product: Ant
Classification: Unclassified
Component: Core (show other bugs)
Version: 1.4.1
Hardware: PC All
: P3 blocker (vote)
Target Milestone: ---
Assignee: Ant Notifications List
URL:
Keywords: JDK1.4
Depends on:
Blocks:
 
Reported: 2002-02-15 10:17 UTC by Thomas Geikenbaum
Modified: 2008-02-22 12:18 UTC (History)
0 users


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 Thomas Geikenbaum 2002-02-15 10:17:12 UTC 
if i start an ant (1.4.1) task from netbeans (3.3.1) or from command line,
windows xp / java 1.4.0 crashes the 16bit subsystem.
Comment 1 Stefan Bodewig 2002-02-15 17:12:04 UTC 
I may be wrong, but could this be a duplicate of Bug 6456?
Comment 2 Stefan Bodewig 2002-02-19 13:10:52 UTC 
To clarify my question: does a recent nightly build work?
Comment 3 Steve Loughran 2002-03-03 07:09:26 UTC 
I am surprised that the 16 bit subsys gets a lookin, let alone crashes; that 
seems to imply that a win16 app is running. XP is not like win9x where the 
windowing system and GDI is all 16 bit code, see.

What is in the build file that causes this?
Comment 4 Jason Ertel 2002-03-25 19:01:40 UTC 
I experienced this bug when I upgraded to XP.  I solved the problem by removing 
the following line from my build.xml files:

<property environment="comp.env"/>

I no longer was given the 16-bit subsystem failure popup and could continue on 
as before, just as when I used Windows 2000 Server as my OS.  I just tried 
putting that line back in my build.xml to re-verify the problem and it isn't 
happening.  Go figure.  In any event, the problem certainly looks to be linked 
with the MSDOS environment and how Java/Ant retrieves variable settings under 
XP.
Comment 5 Steve Loughran 2002-03-26 01:40:55 UTC 
if it is in env, then I am going to mark this bug as a duplicate of 6456

*** This bug has been marked as a duplicate of 6456 ***