All of lore.kernel.org
 help / color / mirror / Atom feed
From: jbrassow@sourceware.org <jbrassow@sourceware.org>
To: lvm-devel@redhat.com
Subject: LVM2/scripts gdbinit
Date: 11 Mar 2011 22:25:36 -0000	[thread overview]
Message-ID: <20110311222536.12369.qmail@sourceware.org> (raw)

CVSROOT:	/cvs/lvm2
Module name:	LVM2
Changes by:	jbrassow at sourceware.org	2011-03-11 22:25:36

Modified files:
	scripts        : gdbinit 

Log message:
	lv_status_r now prints out status of attached log LVs
	
	(Print layout could be nicer... :(

Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/scripts/gdbinit.diff?cvsroot=lvm2&r1=1.3&r2=1.4

--- LVM2/scripts/gdbinit	2011/03/11 22:16:38	1.3
+++ LVM2/scripts/gdbinit	2011/03/11 22:25:36	1.4
@@ -198,10 +198,11 @@
 end
 
 define lv_status
-	set $_lv=(struct logical_volume *)$arg0
+	# Use __lv because we don't want to overwrite higher functions
+	set $__lv = (struct logical_volume *)$arg0
 
-	printf "%s->status:", $_lv->name
-	__status $_lv
+	printf "%s->status:", $__lv->name
+	__status $__lv
 	printf "\n"
 end
 
@@ -371,6 +372,10 @@
 			__seg_item $_lv $_seg $_area_index
 			__lv_status_r $_lv
 		else
+			if ($_seg->log_lv)
+				printf "[LOG OF %s] ", $_lv->name
+				lv_status $_seg->log_lv
+			end
 			__get_only_segment_using_this_lv $_seg $_lv
 			if ($_seg)
 				__lv_status_r $_lv $_seg



             reply	other threads:[~2011-03-11 22:25 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-11 22:25 jbrassow [this message]
  -- strict thread matches above, loose matches on Subject: below --
2012-04-10 23:24 LVM2/scripts gdbinit 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-29 12:53 jbrassow
2011-03-14 18:05 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=20110311222536.12369.qmail@sourceware.org \
    --to=jbrassow@sourceware.org \
    --cc=lvm-devel@redhat.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.