From: Vikas Mishra <vikasm@vikasmishra.org>
To: gdb@sourceware.org
Subject: Re: gdb breaking down at printing variable
Date: Thu, 26 Aug 2010 15:21:00 -0000 [thread overview]
Message-ID: <AANLkTikdFOrga-bM56Jf31FLTmkdPFAx0dTd6WQPcT=i@mail.gmail.com> (raw)
In-Reply-To: <AANLkTimFU22phqb1uScS7PZ5WGJ65+1uD6RtkWMt352h@mail.gmail.com>
Andre'
On Thu, Aug 26, 2010 at 8:47 PM, Vikas Mishra <vikasm@vikasmishra.org> wrote:
> On Thursday 26 August 2010 13:41:29 ext Vikas Mishra wrote:
>> Hello Folks,
>>
>> I am new to C++ but have used gdb in the past. I am using the python
>> pretty print extensions to the GDB to print STL containers. I wanted
>> to check with the mailing list about an issue that I was seeing
>> recently. I am seeing the issue both on Cygwin as well as in Linux.
>>
>> Problem : Unable to print a vector during debugging.
>>
>> How to reproduce it : I have attached a program which has two
>> functions - main and split, It is a very simple program that takes a
>> string and splits it into words (like Perl's split function). I am not
>> able to print the variable "ret" anywhere in the "split" function.
>
> This is most likely http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44731
> i.e. not gdb's fault.
Thanks a lot for pointing this out. The error of course disappeared if
I did a temporary hack and replaced the return with an assignment and
return. This is good enough for me at the moment.
Regards,
Vikas
next parent reply other threads:[~2010-08-26 15:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AANLkTimFU22phqb1uScS7PZ5WGJ65+1uD6RtkWMt352h@mail.gmail.com>
2010-08-26 15:21 ` Vikas Mishra [this message]
2010-08-26 11:41 Vikas Mishra
2010-08-26 12:25 ` André Pönitz
2010-08-26 20:55 ` Tom Tromey
2010-08-27 9:41 ` André Pönitz
2010-08-27 15:22 ` Tom Tromey
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='AANLkTikdFOrga-bM56Jf31FLTmkdPFAx0dTd6WQPcT=i@mail.gmail.com' \
--to=vikasm@vikasmishra.org \
--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