[jboss-jira] [JBoss JIRA] (WFCORE-608) Using ? as control character in .inputrc causes CLI to terminate immediately.

Alexey Loubyansky (JIRA) issues at jboss.org
Wed May 13 03:01:21 EDT 2015


     [ https://issues.jboss.org/browse/WFCORE-608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alexey Loubyansky updated WFCORE-608:
-------------------------------------
    Fix Version/s: 1.0.0.CR4
                       (was: 1.0.0.Beta1)


> Using ? as control character in .inputrc causes CLI to terminate immediately. 
> ------------------------------------------------------------------------------
>
>                 Key: WFCORE-608
>                 URL: https://issues.jboss.org/browse/WFCORE-608
>             Project: WildFly Core
>          Issue Type: Bug
>          Components: CLI
>         Environment: Linux
>            Reporter: Jay Kumar SenSharma
>            Assignee: Alexey Loubyansky
>             Fix For: 1.0.0.CR4
>
>
> - When using  *[wildfly-8.2.0.Final]* When user has a '.inputrc' in the user home directory with the following content:
> {code}
> # Control characters
> "\C-?":   backward-delete-char
> {code}
> - The it fails with the the following Stack Trace:
> {code}
> ./jboss-cli.sh 
> java.lang.RuntimeException: ERROR parsing ? keys to aesh. Check your inputrc.
> 	at org.jboss.aesh.edit.mapper.KeyMapper.convertRandomControlKeys(KeyMapper.java:161)
> 	at org.jboss.aesh.edit.mapper.KeyMapper.mapRandomKeys(KeyMapper.java:138)
> 	at org.jboss.aesh.edit.mapper.KeyMapper.mapKeys(KeyMapper.java:108)
> 	at org.jboss.aesh.edit.mapper.KeyMapper.mapQuoteKeys(KeyMapper.java:49)
> 	at org.jboss.aesh.console.Config.parseInputrc(Config.java:127)
> 	at org.jboss.aesh.console.Console.reset(Console.java:150)
> 	at org.jboss.aesh.console.Console.<init>(Console.java:105)
> 	at org.jboss.aesh.console.Console.<init>(Console.java:101)
> 	at org.jboss.as.cli.impl.Console$Factory.getConsole(Console.java:85)
> 	at org.jboss.as.cli.impl.Console$Factory.getConsole(Console.java:78)
> 	at org.jboss.as.cli.impl.CommandContextImpl.initBasicConsole(CommandContextImpl.java:349)
> 	at org.jboss.as.cli.impl.CommandContextImpl.<init>(CommandContextImpl.java:296)
> 	at org.jboss.as.cli.impl.CommandContextFactoryImpl.newCommandContext(CommandContextFactoryImpl.java:76)
> 	at org.jboss.as.cli.impl.CliLauncher.initCommandContext(CliLauncher.java:273)
> 	at org.jboss.as.cli.impl.CliLauncher.main(CliLauncher.java:253)
> 	at org.jboss.as.cli.CommandLineMain.main(CommandLineMain.java:34)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> 	at java.lang.reflect.Method.invoke(Method.java:606)
> 	at org.jboss.modules.Module.run(Module.java:312)
> 	at org.jboss.modules.Main.main(Main.java:460)
> {code}
> - Expectation is that CLI should not have terminated suddenly rather the exception should have been handled in a proper way.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


More information about the jboss-jira mailing list