From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-return-46833-listarch-gdb=sources.redhat.com@sourceware.org>
Received: (qmail 4813 invoked by alias); 21 Feb 2019 13:12:36 -0000
Mailing-List: contact gdb-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb.sourceware.org>
List-Subscribe: <mailto:gdb-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb/>
List-Post: <mailto:gdb@sourceware.org>
List-Help: <mailto:gdb-help@sourceware.org>, <http://sourceware.org/ml/#faqs>
Sender: gdb-owner@sourceware.org
Received: (qmail 4800 invoked by uid 89); 21 Feb 2019 13:12:35 -0000
Authentication-Results: sourceware.org; auth=none
X-Spam-SWARE-Status: No, score=-0.9 required=5.0 tests=BAYES_00,KAM_LAZY_DOMAIN_SECURITY,RCVD_IN_DNSWL_NONE autolearn=no version=3.3.2 spammy=Hx-languages-length:583, sorts
X-HELO: mail-wr1-f53.google.com
Received: from mail-wr1-f53.google.com (HELO mail-wr1-f53.google.com) (209.85.221.53) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Thu, 21 Feb 2019 13:12:34 +0000
Received: by mail-wr1-f53.google.com with SMTP id q1so30060480wrp.7        for <gdb@sourceware.org>; Thu, 21 Feb 2019 05:12:34 -0800 (PST)
Return-Path: <palves@redhat.com>
Received: from ?IPv6:2001:8a0:f913:f700:75e6:857f:3506:a1f4? ([2001:8a0:f913:f700:75e6:857f:3506:a1f4])        by smtp.gmail.com with ESMTPSA id e6sm25509414wrt.14.2019.02.21.05.12.31        (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);        Thu, 21 Feb 2019 05:12:31 -0800 (PST)
Subject: Re: "finish" command leads to SIGTRAP
To: David Griffiths <dgriffiths@undo.io>
References: <CA++j6c7bhP7=AWWdzBajC7KUah1gwj25-Bpoqd1-Xs_67z5kVw@mail.gmail.com> <b437759f-5223-fcd2-1e68-f77051a2f910@redhat.com> <CA++j6c4co2Uz=3q952pf3skq8xMdsmQ_4+H6eMBkAdvyXMzK8A@mail.gmail.com> <CA++j6c6A0DMRwOGBJ4XGGWnC49D1Wi9J9kz6kzSmaj+kiJXo-w@mail.gmail.com>
Cc: gdb@sourceware.org
From: Pedro Alves <palves@redhat.com>
Message-ID: <78e1f522-f6f5-d38d-0644-d083c1e4ab5d@redhat.com>
Date: Thu, 21 Feb 2019 13:12:00 -0000
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1
MIME-Version: 1.0
In-Reply-To: <CA++j6c6A0DMRwOGBJ4XGGWnC49D1Wi9J9kz6kzSmaj+kiJXo-w@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-SW-Source: 2019-02/txt/msg00041.txt.bz2

Might be unrelated, but ISTR that there used to be a kernel bug
that would lead to the cpu's trace flag getting stuck set
when you step in a signal handler.  That would result in
SIGTRAP happening at every step from that point on.  Could
that be the case here?

I'd look at "set debug displaced on" too.  Otherwise, it's a matter
at staring at the logs, and trying to understand what is happening.
Basically, "finish" sets a breakpoint at the caller and runs to it.
But all sorts of other things can happen behind the scenes.

Thanks,
Pedro Alves