From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from simark.ca by simark.ca with LMTP id 6d2DKs7IjWBZDwAAWB0awg (envelope-from ) for ; Sat, 01 May 2021 17:31:58 -0400 Received: by simark.ca (Postfix, from userid 112) id A194B1F11C; Sat, 1 May 2021 17:31:58 -0400 (EDT) X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on simark.ca X-Spam-Level: X-Spam-Status: No, score=-1.1 required=5.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,MAILING_LIST_MULTI,URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.2 Received: from sourceware.org (server2.sourceware.org [8.43.85.97]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by simark.ca (Postfix) with ESMTPS id E75151E783 for ; Sat, 1 May 2021 17:31:57 -0400 (EDT) Received: from server2.sourceware.org (localhost [IPv6:::1]) by sourceware.org (Postfix) with ESMTP id EFACC3844047; Sat, 1 May 2021 21:31:56 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org EFACC3844047 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1619904717; bh=ajuLhl+xsdVspopfsTV7oB0Oml6HbkQHdq67F+uqY2c=; h=Subject:To:References:Date:In-Reply-To:List-Id:List-Unsubscribe: List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To: From; b=GKkkNcMAWX/KAMOroVHyxANEsRlOr3A3FLd04shJMFXRat9nyX1xdQuGzjU1EMTj3 hLO0ObN3YgMmnUPnHyhcRDC0SedVwbbezhbZbhnevZ1DHn+kS5AeU49jmiN7zaZaL4 rgGnxYkAXYX7QjevClaZ8xNR2gHtUBrJznLQ0aVc= Received: from smtp.polymtl.ca (smtp.polymtl.ca [132.207.4.11]) by sourceware.org (Postfix) with ESMTPS id 217703858034 for ; Sat, 1 May 2021 21:31:54 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 217703858034 Received: from simark.ca (simark.ca [158.69.221.121]) (authenticated bits=0) by smtp.polymtl.ca (8.14.7/8.14.7) with ESMTP id 141LVm95006524 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Sat, 1 May 2021 17:31:53 -0400 DKIM-Filter: OpenDKIM Filter v2.11.0 smtp.polymtl.ca 141LVm95006524 Received: from [10.0.0.11] (192-222-157-6.qc.cable.ebox.net [192.222.157.6]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by simark.ca (Postfix) with ESMTPSA id 4F4811E783; Sat, 1 May 2021 17:31:48 -0400 (EDT) Subject: Re: Trace/breakpoint trap. To: Jason Long , Eli Zaretskii via Gdb References: <895597245.1533806.1619862429301.ref@mail.yahoo.com> <895597245.1533806.1619862429301@mail.yahoo.com> Message-ID: <79240173-07cd-7ac1-b080-450efbb444b1@polymtl.ca> Date: Sat, 1 May 2021 17:31:47 -0400 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.7.1 MIME-Version: 1.0 In-Reply-To: <895597245.1533806.1619862429301@mail.yahoo.com> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-Poly-FromMTA: (simark.ca [158.69.221.121]) at Sat, 1 May 2021 21:31:48 +0000 X-BeenThere: gdb@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gdb mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: Simon Marchi via Gdb Reply-To: Simon Marchi Errors-To: gdb-bounces@sourceware.org Sender: "Gdb" On 2021-05-01 5:47 a.m., Jason Long via Gdb wrote: > Hello, > I installed the Atomic Cryptocurrency Wallet on my Debian Linux and when I want to launch it, then it shows me "Trace/breakpoint trap" error. > I want to find the reason of it with GDB. > I launched it inside the GDB: > > (gdb) run > Starting program: /usr/bin/atomic > [Thread debugging using libthread_db enabled] > Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". > [New Thread 0x7ffff2eb7700 (LWP 12453)] > [Detaching after fork from child process 12454] > > > Thread 1 "atomic" received signal SIGTRAP, Trace/breakpoint trap. > 0x000055555a7556f3 in ?? () > > What is the next step? > > > Thank you. > Hi, You could start by using "bt" to get a sense of where you are stopped. You could try to find out in which object file address 0x000055555a7556f3 falls. You can use "info target" for that. Depending on what you find, the next steps depend on what you find (it's investigative work, so there's not pre-defined path). Simon