public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Jason Long <hack3rcon@yahoo.com>
To: "gdb@sourceware.org" <gdb@sourceware.org>,
	Simon Marchi <simark@simark.ca>
Subject: Re: I'm a beginner and need help about "Segmentation fault" error.
Date: Fri, 6 Nov 2020 18:10:57 +0000 (UTC)	[thread overview]
Message-ID: <780402530.1737902.1604686257419@mail.yahoo.com> (raw)
In-Reply-To: <aa1b0c20-046f-aa65-16dd-22fadeabbf35@simark.ca>

Thank you.
I did what you said:

(gdb) run
Starting program: /usr/local/bin/ramme 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".


Program received signal SIGSEGV, Segmentation fault.
0x0000000000e6e0c0 in ?? ()
(gdb) backtrace 
#0  0x0000000000e6e0c0 in ?? ()
#1  0x00007ffff7d85462 in node::http2::Http2Session::Callbacks::Callbacks(bool)
    () from /opt/Ramme/libnode.so
#2  0x00007ffff7d85525 in ?? () from /opt/Ramme/libnode.so
#3  0x00007ffff7fe437a in call_init (l=<optimized out>, argc=argc@entry=1, 
    argv=argv@entry=0x7fffffffe248, env=env@entry=0x7fffffffe258)
    at dl-init.c:72
#4  0x00007ffff7fe4476 in call_init (env=0x7fffffffe258, argv=0x7fffffffe248, 
    argc=1, l=<optimized out>) at dl-init.c:30
#5  _dl_init (main_map=0x7ffff7ffe190, argc=1, argv=0x7fffffffe248, 
    env=0x7fffffffe258) at dl-init.c:119
#6  0x00007ffff7fd60ca in _dl_start_user () from /lib64/ld-linux-x86-64.so.2
#7  0x0000000000000001 in ?? ()
#8  0x00007fffffffe52b in ?? ()
#9  0x0000000000000000 in ?? ()


What is the next step?






On Thursday, November 5, 2020, 05:13:30 PM GMT+3:30, Simon Marchi <simark@simark.ca> wrote: 






On 2020-11-03 11:54 a.m., Jason Long via Gdb wrote:
> Hello,
> I'm using Debian 10.6 x86_64 and when I want to run a program then it show me "Segmentation fault" error.
> How can use gdb to find the reason of it?
> I used strace to generate an output and posted it here: https://pastebin.fun/NY4RUEmyzO
>
> I'm thankful if anyone advice me step by step.
>
> Thank you.

>

Hi Jason,

In its most simple expressioj, just load the program in GDB:

  $ gdb <program>

and run it:

  (gdb) run

If the program crashes (receives a SIGSEGV / segmentation fault signal),
it will stop and you'll be able to inspect the state of the program at
that moment.  For example, you'll be able to use the "backtrace" command
to get an idea of wherwe the program was.

Simon


  reply	other threads:[~2020-11-06 18:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <394886388.1091427.1604422440532.ref@mail.yahoo.com>
2020-11-03 16:54 ` Jason Long
2020-11-05 13:43   ` Simon Marchi
2020-11-06 18:10     ` Jason Long [this message]
2020-11-07  1:16       ` Simon Marchi
2020-11-09 11:55         ` Anton.Krug

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=780402530.1737902.1604686257419@mail.yahoo.com \
    --to=hack3rcon@yahoo.com \
    --cc=gdb@sourceware.org \
    --cc=simark@simark.ca \
    /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).