From: "Peter Toft" <pto@linuxbog.dk>
To: gdb@sourceware.org
Subject: gdb printing of dynamically allocated matrix
Date: Wed, 18 Jul 2007 17:59:00 -0000 [thread overview]
Message-ID: <fd760b5c0707180422x49899ec4ob1052aa25cfda772@mail.gmail.com> (raw)
Focus of this mail is GDB on 1D and 2D arrays.
I have pasted a small C-code program at
http://pastebin.com/f63009dd8
(download from http://pastebin.com/pastebin.php?dl=f63009dd8)
which I like your opinion on.
I compile it with "gcc -g"
Throw a breakpoint on line 59 and run under gdb.
* I can see the contents of the "a"-vector in by
(gdb) print *a @ 3
Very cool!
* I can see the matrix (2D array) contents of the "c"
matrix by
(gdb) print c
Elegant - very cool!
* However how can I use GDB to see the contents of "b"
similar to the contents of "c" and "a"?
The best I can do is
(gdb) print *b[0] @3
(gdb) print *b[1] @3
Obviously I would like to do the display in one command rather
than several, especially if I changed the b-matrix to be b[7][8]
I think I will manually have to supply the length of the vectors,
but it seems that I cannot do a compound GDB-operation like
(gdb) print **b @3 @2
and get
{{2, -2, 22},{12 -12 -12}}
instead I get
{{2, -2, 22},{17# 12# -12}}
where I have inserted #-marks where I find wrong values.
How come that the next vector contains wrong values?
Or rather - how can I see the b content in one command?
Best
--
Peter Toft <pto@linuxbog.dk>
next reply other threads:[~2007-07-18 11:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-18 17:59 Peter Toft [this message]
2007-07-18 19:32 ` Daniel Jacobowitz
2007-07-18 20:32 ` Peter Toft
2007-07-18 21:56 ` Peter Toft
2007-07-19 3:10 ` Daniel Jacobowitz
2007-07-20 18:48 ` Peter Toft
2007-07-20 19:08 ` Jim Blandy
2007-07-21 14:16 ` Peter Toft
2007-07-23 17:05 ` Jim Blandy
2007-07-23 21:38 ` Peter Toft
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=fd760b5c0707180422x49899ec4ob1052aa25cfda772@mail.gmail.com \
--to=pto@linuxbog.dk \
--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