public inbox for lvm2-cvs@sourceware.org
help / color / mirror / Atom feed
From: jbrassow@sourceware.org
To: lvm-devel@redhat.com, lvm2-cvs@sourceware.org
Subject: LVM2/scripts gdbinit
Date: Tue, 29 Mar 2011 12:53:00 -0000 [thread overview]
Message-ID: <20110329125313.16497.qmail@sourceware.org> (raw)
CVSROOT: /cvs/lvm2
Module name: LVM2
Changes by: jbrassow@sourceware.org 2011-03-29 12:53:13
Modified files:
scripts : gdbinit
Log message:
gdbinit update
When doing lv_status_r on a sub_lv, do not climb the tree up past the
starting point.
Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/scripts/gdbinit.diff?cvsroot=lvm2&r1=1.5&r2=1.6
--- LVM2/scripts/gdbinit 2011/03/14 18:05:56 1.5
+++ LVM2/scripts/gdbinit 2011/03/29 12:53:13 1.6
@@ -31,6 +31,7 @@
printf "break check_lv_segments\n"
printf "break text_import_areas\n"
printf "run --type raid1 -L 200M -n lv vg\n"
+printf "run -m1 -L 200M -n lv vg\n"
printf "lv_status_r lv\n"
printf "\n\n"
@@ -390,8 +391,15 @@
if ($_s == $_seg_list_head)
if ($argc == 1)
+ __print_indent $indent 1
printf "[ No segments for %s ]\n", $_lv->name
end
+ __get_only_segment_using_this_lv $_seg $_lv
+
+ if ($_seg && $indent)
+ set $indent--
+ __lv_status_r $_lv $_seg
+ end
else
set $_seg = (struct lv_segment *)$_s
set $_type = 0x0
next reply other threads:[~2011-03-29 12:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-29 12:53 jbrassow [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-04-10 23:24 jbrassow
2011-09-28 16:32 jbrassow
2011-09-13 13:57 jbrassow
2011-09-08 22:19 jbrassow
2011-09-01 21:01 jbrassow
2011-07-01 16:15 jbrassow
2011-03-14 18:05 jbrassow
2011-03-11 22:25 jbrassow
2011-03-11 22:16 jbrassow
2011-03-11 18:22 jbrassow
2011-03-10 13:45 jbrassow
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=20110329125313.16497.qmail@sourceware.org \
--to=jbrassow@sourceware.org \
--cc=lvm-devel@redhat.com \
--cc=lvm2-cvs@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).