Tarantool development patches archive
 help / color / mirror / Atom feed
From: Sergey Kaplun via Tarantool-patches <tarantool-patches@dev.tarantool.org>
To: sergos <sergos@tarantool.org>
Cc: tarantool-patches@dev.tarantool.org
Subject: Re: [Tarantool-patches] [PATCH luajit] Fix debug.debug() for non-string errors.
Date: Wed, 22 Jun 2022 11:24:31 +0300	[thread overview]
Message-ID: <YrLRvwy3KA6TF8JL@root> (raw)
In-Reply-To: <4E9E5823-C595-4F01-AA26-62D2BEA2DA28@tarantool.org>

Hi, Sergos!

Thanks for the review!

On 21.06.22, sergos wrote:
> Hi!
> 
> Thanks for the patch!
> 
> It’s strange, but Tarantool happens to handle this case correctly?

Not for me:).

| $ echo 'error({}); print(42)' | ./src/tarantool -e 'debug.debug()'
| lua_debug> Segmentation fault
| ...
| #5  0x55a6323a6b84 in lj_cf_debug_debug+ef
| #6  0x55a63236b66f in lj_BC_FUNCC+34
| #7  0x55a63237687b in lua_pcall+379
| #8  0x55a632305317 in luaT_call+29
| #9  0x55a6322fd8b7 in run_script_f+427
| #10 0x55a6320f496e in _ZL16fiber_cxx_invokePFiP13__va_list_tagES0_+1e
| #11 0x55a63232b3f0 in fiber_loop+8d
| #12 0x55a632686716 in coro_init+4c

May be you should build it with debug?

| $ src/tarantool -v
| Tarantool 2.10.0-beta2-6-g634f59c7f
| Target: Linux-x86_64-Debug
| Build options: cmake . -DCMAKE_INSTALL_PREFIX=/usr/local -DENABLE_BACKTRACE=ON

P.S. I use not the latest Tarantool as far as there is no related
patches (AFAIK).

> 
> % echo 'error({}); print(42)' | ./src/tarantool -e 'debug.debug()' 
> lua_debug> (null)
> lua_debug> %                                                                                                                                                                                                                                                              % echo $?
> 0
> 
> Surely, with the patch applied I see the following, as expected:
> 
> % echo 'error({}); print(42)' | ./src/tarantool -e 'debug.debug()'
> lua_debug> (error object is not a string)
> lua_debug> %                                                                                                                                                                                                                                                              % 
> 
> 
> Is it relevant at all?
> 
> regards,
> Sergos
> 
> 
> > On 30 Dec 2021, at 14:45, Sergey Kaplun <skaplun@tarantool.org> wrote:
> > 

<snipped>

> 

-- 
Best regards,
Sergey Kaplun

  reply	other threads:[~2022-06-22  8:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-30 11:45 Sergey Kaplun via Tarantool-patches
2022-06-21 12:01 ` sergos via Tarantool-patches
2022-06-22  8:24   ` Sergey Kaplun via Tarantool-patches [this message]
2022-06-28 23:05 ` Igor Munkin via Tarantool-patches
2022-06-30 12:10 ` Igor Munkin via Tarantool-patches

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=YrLRvwy3KA6TF8JL@root \
    --to=tarantool-patches@dev.tarantool.org \
    --cc=sergos@tarantool.org \
    --cc=skaplun@tarantool.org \
    --subject='Re: [Tarantool-patches] [PATCH luajit] Fix debug.debug() for non-string errors.' \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox