From: D Haley <mycae@yahoo.com>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb@sourceware.org
Subject: Re: c++ member arrays with variable size
Date: Sun, 04 Nov 2007 11:26:00 -0000 [thread overview]
Message-ID: <75699.86396.qm@web36804.mail.mud.yahoo.com> (raw)
In-Reply-To: <20071104031022.GB8183@caradoc.them.org>
Hi Daniel,
> Most of the time, if a variable does not show up in
> "info locals",
> that means your compiler has not emitted debug info
> for it. I tried
> your example with G++ 4.2 on x86_64-linux, and did
> see the local
> array.
Hmm, I tried on another machine and yes, i can see it.
For the record on the non-working version I am using
apple-darwin8-g++ (GCC) 4.0.1. Minus one point for
apple :( .
Thanks.
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
next prev parent reply other threads:[~2007-11-04 11:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-04 1:52 D Haley
2007-11-04 3:10 ` Daniel Jacobowitz
2007-11-04 11:26 ` D Haley [this message]
2007-11-04 14:34 ` Daniel Jacobowitz
2007-11-05 18:55 ` Jim Ingham
2007-11-09 6:42 ` D Haley
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=75699.86396.qm@web36804.mail.mud.yahoo.com \
--to=mycae@yahoo.com \
--cc=drow@false.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).