From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp47.i.mail.ru (smtp47.i.mail.ru [94.100.177.107]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dev.tarantool.org (Postfix) with ESMTPS id 17AF0445320 for ; Mon, 6 Jul 2020 08:50:42 +0300 (MSK) From: Oleg Babin References: Message-ID: <8c8cbc95-3d7b-6c92-669c-c040efdf8147@tarantool.org> Date: Mon, 6 Jul 2020 08:50:41 +0300 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-GB Subject: Re: [Tarantool-patches] [PATCH] gdb: fix the extension to be loaded with Python 2 List-Id: Tarantool development patches List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Igor Munkin , Sergey Ostanevich , Alexander Turenko Cc: tarantool-patches@dev.tarantool.org Hi! Thanks for your patch! I just add that problem appeared on CentOS 7 that is still popular. But seems your patch solves a problem. LGTM. On 04/07/2020 22:58, Igor Munkin wrote: > There was a mystic error when the extension was loaded against old gdb > versions build against Python 2: > | (gdb) source luajit-gdb.py > | Traceback (most recent call last): > | File "luajit-gdb.py", line 702, in > | load(None) > | File "luajit-gdb.py", line 699, in load > | 'lj-gc': LJGC, > | File "luajit-gdb.py", line 687, in init > | command(name) > | File "luajit-gdb.py", line 468, in __init__ > | gdb.write('{} command initialized\n'.format(name)) > | ValueError: sequence.index(x): x not in sequence