From: Jason Long <hack3rcon@yahoo.com>
To: Eli Zaretskii via Gdb <gdb@sourceware.org>
Subject: Trace/breakpoint trap.
Date: Sat, 1 May 2021 09:47:09 +0000 (UTC) [thread overview]
Message-ID: <895597245.1533806.1619862429301@mail.yahoo.com> (raw)
In-Reply-To: <895597245.1533806.1619862429301.ref@mail.yahoo.com>
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.
next parent reply other threads:[~2021-05-01 9:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <895597245.1533806.1619862429301.ref@mail.yahoo.com>
2021-05-01 9:47 ` Jason Long [this message]
2021-05-01 21:31 ` Simon Marchi
2021-05-14 19:45 ` Jason Long
2021-05-14 19:52 ` Simon Marchi
2021-05-14 20:08 ` Jason Long
2021-05-14 22:01 ` Jeffrey Walton
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=895597245.1533806.1619862429301@mail.yahoo.com \
--to=hack3rcon@yahoo.com \
--cc=gdb@sourceware.org \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).