From: Oliver Block <lists@block-online.eu>
To: gdb@sourceware.org
Subject: how to show cause of segmentation fault with gdb
Date: Tue, 20 Jun 2006 22:55:00 -0000 [thread overview]
Message-ID: <200606210052.45882.lists@block-online.eu> (raw)
Hi,
the last days I faced the following problem. I was writing a program that used
c-client library. I defined and assigned a
char *myvar;
and the function expected a
char myvar[];
Because a deeper function needed write access to that variable the program
stopped with a segmentation fault. Someone else gave me a hint which is most
likely the cause of the error. But he guessed, actually.
Is there a safe way show the cause of that error using gdb.
Best Regards,
Oliver
next reply other threads:[~2006-06-20 22:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-20 22:55 Oliver Block [this message]
2006-06-20 23:28 ` Daniel Jacobowitz
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=200606210052.45882.lists@block-online.eu \
--to=lists@block-online.eu \
--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