From: <Anton.Krug@microchip.com>
To: <simark@simark.ca>, <hack3rcon@yahoo.com>, <gdb@sourceware.org>
Subject: Re: I'm a beginner and need help about "Segmentation fault" error.
Date: Mon, 9 Nov 2020 11:55:10 +0000 [thread overview]
Message-ID: <MWHPR1101MB2270190997E61D3902FB0DA982EA0@MWHPR1101MB2270.namprd11.prod.outlook.com> (raw)
In-Reply-To: <f30c8a3b-ac90-14a8-bcd3-e47a807c616b@simark.ca>
And when the -g is enabled, do not strip the symbols from the binary. So remove '-s' if you have in the compilation process, and remove 'strip' commands which might be triggered on the compiled object files after they were compiled.
________________________________
From: Gdb <gdb-bounces@sourceware.org> on behalf of Simon Marchi <simark@simark.ca>
Sent: 07 November 2020 01:16
To: Jason Long <hack3rcon@yahoo.com>; gdb@sourceware.org <gdb@sourceware.org>
Subject: Re: I'm a beginner and need help about "Segmentation fault" error.
EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
On 2020-11-06 1:10 p.m., Jason Long via Gdb wrote:
> 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?
The next step would be to compile your program with debug info (-g3) and
without optimization (-O0).
I also suggest you search and read for any GDB tutorial out there, it
will walk you though these steps.
Simon
prev parent reply other threads:[~2020-11-09 11:55 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
2020-11-07 1:16 ` Simon Marchi
2020-11-09 11:55 ` Anton.Krug [this message]
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=MWHPR1101MB2270190997E61D3902FB0DA982EA0@MWHPR1101MB2270.namprd11.prod.outlook.com \
--to=anton.krug@microchip.com \
--cc=gdb@sourceware.org \
--cc=hack3rcon@yahoo.com \
--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).