this should be fixed on the develop branch now. Thanks!
On Wed, May 31, 2017 at 8:47 AM, Jens Deppe wrote:
> OK, thanks Jinmei.
>
> --Jens
>
> On Wed, May 31, 2017 at 8:42 AM, Jinmei Liao wrote:
>
> > I believe this is due to bug I introduced when working on gfsh parser
> when
> > dealing with
OK, thanks Jinmei.
--Jens
On Wed, May 31, 2017 at 8:42 AM, Jinmei Liao wrote:
> I believe this is due to bug I introduced when working on gfsh parser when
> dealing with --J option that has comma in the values. Will get a fix in
> soon.
>
> On Wed, May 31, 2017 at 7:41 AM, Jens Deppe wrote:
>
I believe this is due to bug I introduced when working on gfsh parser when
dealing with --J option that has comma in the values. Will get a fix in
soon.
On Wed, May 31, 2017 at 7:41 AM, Jens Deppe wrote:
> Hi,
>
> In the past, when launching a server or locator with gfsh, I could specify
> debug
Hi,
In the past, when launching a server or locator with gfsh, I could specify
debugging options like this:
gfsh start locator --name=locator1 \
--J=\"-agentlib:jdwp=transport=dt_socket,server=y,suspend=n,address=5005\"
I had to specially quote the agentlib options otherwise the commas would
