Mailing-List: contact dev-help@asterixdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@asterixdb.apache.org
Sender: Ildar Absalyamov <ty13r.derden@gmail.com>
From: Ildar Absalyamov <ildar.absalyamov@gmail.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 10.0 \(3226\))
Subject: Re: Debugging with generated code
Date: Mon, 17 Oct 2016 22:39:06 -0700
References: <CAN-bgPq5czv5uie3s3nSDuUiq5AXXM8R8mjnA7JMe+dneBhU4w@mail.gmail.com>
 <CAFUTFebej0aXJeo1qeUAB3om7e5iQxsHAk0Z02x6xP4J9O0JGQ@mail.gmail.com>
To: dev@asterixdb.apache.org
In-Reply-To: <CAFUTFebej0aXJeo1qeUAB3om7e5iQxsHAk0Z02x6xP4J9O0JGQ@mail.gmail.com>
Message-Id: <2328A548-2F05-4A6B-9B5F-CF25B043A11A@gmail.com>
archived-at: Tue, 18 Oct 2016 05:39:15 -0000

Hit that issue as well.
Is there any workaround to configure the debugger to pick up generated =
byte code?
Or alternatively have a flag which disables runtime codegen during debug =
sessions?

> On Sep 13, 2016, at 19:00, Michael Blow <mblow.apache@gmail.com> =
wrote:
>=20
> I believed ASTERIX-1459 to be fixed, but it seems there are some =
issues.
> When running the execution tests, if I step into a generated =
evaluator, I
> can set breakpoints as normal.  But, when running a one-off single =
test, it
> seems while I can step into the generated evaluators, I cannot set
> breakpoints.  I will re-open 1459 for further investigation.
>=20
> Thanks,
>=20
> -MDB
>=20
> On Tue, Sep 13, 2016 at 6:16 PM Xikui Wang <xikuiw@uci.edu> wrote:
>=20
>> Hi Devs,
>>=20
>> I am debugging with FieldAccessByIndexEvalFactory, and the break =
points are
>> not working here. This may be related to  ASTERIXDB-1459
>> <https://issues.apache.org/jira/browse/ASTERIXDB-1459>. Is this fixed =
in
>> the code base? Thanks.
>>=20
>> Best,
>> Xikui
>>=20

Best regards,
Ildar