From: Baurzhan Ismagulov <ibr@radix50.net>
To: gdb@sourceware.org
Subject: Re: Using gdb to debug Segmentation fault on linux
Date: Wed, 03 Oct 2007 09:41:00 -0000 [thread overview]
Message-ID: <20071003094117.GA4885@radix50.net> (raw)
In-Reply-To: <568e62a40710021646t2feea2f5re5a7c71d77bee72d@mail.gmail.com>
Hello Ying,
On Tue, Oct 02, 2007 at 06:46:22PM -0500, ying lcs wrote:
> Program received signal SIGSEGV, Segmentation fault.
> [Switching to Thread -1218548816 (LWP 25361)]
> 0x08067623 in RTPStream::SendRTCPSR (this=0x83a1520, inTime=@0x1b9a5b58,
> inAppendBye=0) at RTCPUtilitiesLib/RTCPSRPacket.h:123
> 123 ((UInt32*)&fSenderReportBuffer)[(fSenderReportWithServerInfoSize
> >> 2) + 1] = htonl(inSSRC);
First, you need to understand what SIGSEGV is. See, e.g.,
http://en.wikipedia.org/wiki/SIGSEGV .
Second, you need to understand what exactly caused it. "p
&((UInt32*)&fSenderReportBuffer)[(fSenderReportWithServerInfoSize >> 2)
+ 1]" at the gdb prompt might give a hint (compare it with the value of
fSenderReportBuffer and sizeof fSenderReportBuffer).
Only when these two are clear it would make sense to look at the bt,
which may or may not help.
With kind regards,
--
Baurzhan Ismagulov
http://www.kz-easy.com/
prev parent reply other threads:[~2007-10-03 9:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-02 23:46 ying lcs
2007-10-03 6:17 ` Jim Blandy
2007-10-03 9:41 ` Baurzhan Ismagulov [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=20071003094117.GA4885@radix50.net \
--to=ibr@radix50.net \
--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