Tarantool development patches archive
 help / color / mirror / Atom feed
From: Sergey Voinov <sergeiv@tarantool.org>
To: tarantool-patches@dev.tarantool.org,
	Alexander Turenko <alexander.turenko@tarantool.org>
Subject: [Tarantool-patches] [PATCH] Increase limits for debug.traceback
Date: Wed, 22 Jan 2020 17:51:59 +0300	[thread overview]
Message-ID: <20200122145159.15751-1-sergeiv@tarantool.org> (raw)

Currently debug.traceback cuts out path prefixes
and removes intermediate frames. This makes it harder
to debug and navigate to files right from terminal.

This change in main trunk adds default traceback
limits as defines to cmake/luajit.cmake file.

Please see the commit for #4581 for luajit submodule.

Closes: #4581
---
 issue: https://github.com/tarantool/tarantool/issues/4581
 branch: https://github.com/tarantool/tarantool/tree/servoin/gh-4581-debug-limits_2
 cmake/luajit.cmake | 7 +++++++
 1 file changed, 7 insertions(+)

diff --git a/cmake/luajit.cmake b/cmake/luajit.cmake
index 072db8269..373e88458 100644
--- a/cmake/luajit.cmake
+++ b/cmake/luajit.cmake
@@ -282,6 +282,13 @@ macro(luajit_build)
         DESTINATION ${MODULE_INCLUDEDIR})
 endmacro()
 
+#
+# Definitions for luajit debug traceback limits
+#
+add_definitions(-DLUA_TRACEBACK_LEVELS1=25)
+add_definitions(-DLUA_TRACEBACK_LEVELS2=25)
+add_definitions(-DLUA_IDSIZE=128)
+
 #
 # Building shipped luajit only if there is no
 # usable system one (see cmake/luajit.cmake) or by demand.
-- 
2.17.1

             reply	other threads:[~2020-01-22 14:51 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-22 14:51 Sergey Voinov [this message]
2020-01-25 19:35 ` Igor Munkin
2020-02-21 11:00 ` Sergey Ostanevich
  -- strict thread matches above, loose matches on Subject: below --
2019-12-13  8:56 Sergey Voinov
2019-12-20 12:25 ` Igor Munkin
2020-01-21  8:08   ` Sergey Voinov
2020-01-15 10:17 ` Sergey Ostanevich
2020-01-20 10:22   ` Sergey Voinov

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=20200122145159.15751-1-sergeiv@tarantool.org \
    --to=sergeiv@tarantool.org \
    --cc=alexander.turenko@tarantool.org \
    --cc=tarantool-patches@dev.tarantool.org \
    --subject='Re: [Tarantool-patches] [PATCH] Increase limits for debug.traceback' \
    /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