Bugzilla – Bug 4719
globus runs /usr/bin/env without checking for \u
Last modified: 2012-09-05 11:43:17
You need to
before you can comment on or make changes to this bug.
# export PS1='\u@\h:\w> '
Unable to update map filejava.lang.IllegalArgumentException: Malformed \uxxxx
java.lang.IllegalArgumentException: Malformed \uxxxx encoding.
line 234 in
is "loadEnvironment();" and loadEnvironment runs /usr/bin/env without checking
whether it returns environment variables that contain "\u...", which
unfortunately is very common, cf. the PS1 example above. I expect this bug to
appear in all java components that run /usr/bin/env, not just in gram.
(In reply to comment #0)
After searching through the code this appears to be less serious than I first
FileMappingConfig.java (and its sibling in source-trees-thr) appears to be the
only file that runs /usr/bin/env. If FileMappingConfig.java is run only at
setup time, i.e., is never run by a regular user, then one can work around the
bug by first changing those environment variables that contain \u (and possibly
other escape sequences). Nevertheless this ought to be fixed.
Reassigning to current GRAM developer to close/fix as appropriate.
Doing some bugzilla cleanup... Resolving old GRAM3 and GRAM4 issues that are
no longer relevant since we've moved on to GRAM5. Also, we're now tracking
issue in jira. Any new issues should be added here: