public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
* [Help]: seg fault in libc in gcc
@ 2020-07-10 14:08 Kunal Chauhan
  2020-07-11  1:46 ` Jim Wilson
  0 siblings, 1 reply; 2+ messages in thread
From: Kunal Chauhan @ 2020-07-10 14:08 UTC (permalink / raw)
  To: gcc-help

Hi Team,


After compilation and running my binary below crash that I am not
understood , by internet also bug is very confusing to me.

some time it show  with binary or some time says the binary name.


log:

Jul 10 12:44:42 madlte1 lte_tr069[12784]: [TID-13038]:
[ipr_cwmp_retrive_rsc_madLte_config(4895)]: Exiting
ipr_cwmp_retrive_rsc_madLte_config

*Jul 10 12:44:42 madlte1 kernel: vRSC[13038]: segfault at 0 ip
00007f2110c99076 sp 00007f210ccea698 error 4 in libc-2.17.so
<http://libc-2.17.so>[7f2110b67000+1b6000]*

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: [Help]: seg fault in libc in gcc
  2020-07-10 14:08 [Help]: seg fault in libc in gcc Kunal Chauhan
@ 2020-07-11  1:46 ` Jim Wilson
  0 siblings, 0 replies; 2+ messages in thread
From: Jim Wilson @ 2020-07-11  1:46 UTC (permalink / raw)
  To: Kunal Chauhan; +Cc: gcc-help

On Fri, Jul 10, 2020 at 7:08 AM Kunal Chauhan via Gcc-help
<gcc-help@gcc.gnu.org> wrote:
> *Jul 10 12:44:42 madlte1 kernel: vRSC[13038]: segfault at 0 ip
> 00007f2110c99076 sp 00007f210ccea698 error 4 in libc-2.17.so
> <http://libc-2.17.so>[7f2110b67000+1b6000]*

Here is an explanation of the kernel message.
https://utcc.utoronto.ca/~cks/space/blog/linux/KernelSegfaultMessageMeaning

Try compiling your program with -g and then running it inside gdb.
This will show you where it is failing which should make it easier to
find the problem.

Jim

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2020-07-11  1:46 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-07-10 14:08 [Help]: seg fault in libc in gcc Kunal Chauhan
2020-07-11  1:46 ` Jim Wilson

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).