From: "ying lcs" <yinglcs@gmail.com>
To: gdb@sourceware.org
Subject: Using gdb to debug Segmentation fault on linux
Date: Tue, 02 Oct 2007 23:46:00 -0000 [thread overview]
Message-ID: <568e62a40710021646t2feea2f5re5a7c71d77bee72d@mail.gmail.com> (raw)
Hi,
I am trying to use gdb to debug a segmentation fault on linux:
I get this backtrace dump, but I don't see what's wrong and why i get
a segmentation fault.
The address of 'this' looks correct. So I would need some help in how
to proceed in troubleshooting this problem:
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);
(gdb)
(gdb) bt
#0 0x08067623 in RTPStream::SendRTCPSR (this=0x83a1520, inTime=@0x1b9a5b58,
inAppendBye=0) at RTCPUtilitiesLib/RTCPSRPacket.h:123
#1 0x08067d40 in RTPStream::Write (this=0x83a1520, inBuffer=0x839d688,
inLen=45, outLenWritten=0x0, inFlags=Variable "inFlags" is not available.
) at Server.tproj/RTPStream.cpp:1093
#2 0x0804c47f in QTSSCallbacks::QTSS_Write (inStream=0x83a1520,
inBuffer=0x839d688, inLen=45, outLenWritten=0x0, inFlags=5)
at Server.tproj/QTSSCallbacks.cpp:343
#3 0x080a28b6 in QTSSFileModuleDispatch (inRole=1936027236,
inParamBlock=0xb75e6360)
at APIModules/QTSSFileModule/QTSSFileModule.cpp:1569
#4 0x080608ed in RTPSession::Run (this=0x83945b0)
at Server.tproj/QTSSModule.h:92
#5 0x080eb1c3 in TaskThread::Entry (this=0x8361258) at Task.cpp:179
#6 0x080e82af in OSThread::_Entry (inThread=0x8361258) at OSThread.cpp:254
#7 0x00106341 in start_thread () from /lib/tls/libpthread.so.0
#8 0x00c966fe in clone () from /lib/tls/libc.so.6
next reply other threads:[~2007-10-02 23:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-02 23:46 ying lcs [this message]
2007-10-03 6:17 ` Jim Blandy
2007-10-03 9:41 ` Baurzhan Ismagulov
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=568e62a40710021646t2feea2f5re5a7c71d77bee72d@mail.gmail.com \
--to=yinglcs@gmail.com \
--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