From: Burlen Loring <burlen.loring@kitware.com>
To: gdb@sourceware.org
Subject: SIGTRAP
Date: Tue, 29 Jul 2008 19:11:00 -0000 [thread overview]
Message-ID: <488F6A0E.9060605@kitware.com> (raw)
Hi,
gdb seems to be having issues when I try to look inside stl vectors. I
see this message
Program received signal SIGTRAP, Trace/breakpoint trap.
Then I end up inside operator[] code. Then the debugger becomes useless
every next results in a SIGTRAP. I think this is new, but it could be
that I am using vectors more lately but either way it's annoying. is
this a known issue? is there a work around?
tycho:~$gdb -v
GNU gdb 6.8-debian
Copyright (C) 2008 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later
<http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "i486-linux-gnu".
thanks
--
Burlen Loring
Kitware, Inc.
R&D Engineer
28 Corporate Drive
Clifton Park, NY 12065-8662
Phone: 518-371-3971 x137
next reply other threads:[~2008-07-29 19:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-29 19:11 Burlen Loring [this message]
2008-07-30 12:13 ` SIGTRAP Daniel Jacobowitz
2008-07-30 12:54 ` SIGTRAP Burlen Loring
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=488F6A0E.9060605@kitware.com \
--to=burlen.loring@kitware.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