FM / util-linux

/usr/share/doc/util-linux

Name	Size	Mode	Actions
examples/	-	0755	rm
releases/	-	0755	rm
00-about-docs.txt	260	0644	edit dl rm
AUTHORS.gz	15113	0644	edit dl rm
blkid.txt	3258	0644	edit dl rm
cal.txt	2262	0644	edit dl rm
changelog.Debian.gz	2654	0644	edit dl rm
col.txt	1913	0644	edit dl rm
copyright	23045	0644	edit dl rm
deprecated.txt	3086	0644	edit dl rm
getopt.txt	992	0644	edit dl rm
getopt_changelog.txt	1927	0644	edit dl rm
howto-build-sys.txt	3193	0644	edit dl rm
howto-compilation.txt	2945	0644	edit dl rm
howto-contribute.txt.gz	3437	0644	edit dl rm
howto-debug.txt	2437	0644	edit dl rm
howto-man-page.txt	126	0644	edit dl rm
howto-pull-request.txt.gz	4260	0644	edit dl rm
howto-tests.txt.gz	1706	0644	edit dl rm
howto-usage-function.txt.gz	2328	0644	edit dl rm
hwclock.txt	147	0644	edit dl rm
modems-with-agetty.txt	2614	0644	edit dl rm
mount.txt	521	0644	edit dl rm
NEWS.Debian.gz	1897	0644	edit dl rm
PAM-configuration.txt	671	0644	edit dl rm
parse-date.txt.gz	8124	0644	edit dl rm
pg.txt	448	0644	edit dl rm
poeigl.txt.gz	8867	0644	edit dl rm
README.Debian	481	0644	edit dl rm
release-schedule.txt	1354	0644	edit dl rm

Edit: /usr/share/doc/util-linux/howto-debug.txt (2437B)

Debugging util-linux programs
=============================

How to deal libtool
-------------------

There are considerations to be made when profiling or debugging some programs
found in the util-linux package. Because wrapper scripts are used for the
binaries to make sure all library dependencies are met, you cannot use tools
such as gdb or valgrind directly with them.

Let's take for example the mount command:

$> cd /path/to/util-linux
	$> file mount/mount
	mount/mount: Bourne-Again shell script text executable

The binary itself is located in the mount/.libs/ directory:

$> file mount/.libs/mount
	mount/.libs/mount: ELF 64-bit LSB executable, x86-64, version 1 \
	(SYSV), dynamically linked (uses shared libs) [...]

When this command is run, there's a library dependency error:

$> mount/.libs/mount
	mount/.libs/mount: /lib/libblkid.so.1: version `BLKID_2.20' not found \
	(required by mount/.libs/mount)

To overcome this we need set the LD_LIBRARY_PATH variable to read the path of
the shared lib found in the sources, and not system-wide:

$> export LD_LIBRARY_PATH=$PWD/libblkid/src/.libs/:$LD_LIBRARY_PATH

Now external debugging tools can be run on the binary.

Happy hacking!
Davidlohr Bueso, August 2011

The libmount & libblkid
-----------------------

Both of the libraries can be debugged by setting an environment variable
consisting of a number. The number will be used as a bit mask, so the more 1 the
higher the debugging level. Search for `DEBUG' from files

libblkid/src/blkidP.h
	libmount/src/mountP.h

to see what the different bits mean. At the time of writing this the following
enabled full debug.

export LIBBLKID_DEBUG=all
	export LIBMOUNT_DEBUG=all
	export LIBFDISK_DEBUG=all
	export LIBSMARTCOLS_DEBUG=all

The libblkid reads by default /etc/blkid.conf which can be overridden by the
environment variable BLKID_CONF. See manual libblkid/libblkid.3 for details
about the configuration file.

Block device information is normally kept in a cache file (see blkid man page
for more information about the cache file location) that can be overridden by
the environment variable BLKID_FILE.

To libmount uses three paths, which can be overridden by using environment
variables. Notice that these environment variables are ignored for non-root
users.

env variable		if not set defaults to
	LIBMOUNT_FSTAB		/etc/fstab
	LIBMOUNT_MTAB		/etc/mtab
	LIBMOUNT_UTAB		/run/mount/utab or /dev/.mount/utab

Debugging util-linux programs ============================= How to deal libtool ------------------- There are considerations to be made when profiling or debugging some programs found in the util-linux package. Because wrapper scripts are used for the binaries to make sure all library dependencies are met, you cannot use tools such as gdb or valgrind directly with them. Let's take for example the mount command: $> cd /path/to/util-linux $> file mount/mount mount/mount: Bourne-Again shell script text executable The binary itself is located in the mount/.libs/ directory: $> file mount/.libs/mount mount/.libs/mount: ELF 64-bit LSB executable, x86-64, version 1 \ (SYSV), dynamically linked (uses shared libs) [...] When this command is run, there's a library dependency error: $> mount/.libs/mount mount/.libs/mount: /lib/libblkid.so.1: version `BLKID_2.20' not found \ (required by mount/.libs/mount) To overcome this we need set the LD_LIBRARY_PATH variable to read the path of the shared lib found in the sources, and not system-wide: $> export LD_LIBRARY_PATH=$PWD/libblkid/src/.libs/:$LD_LIBRARY_PATH Now external debugging tools can be run on the binary. Happy hacking! Davidlohr Bueso, August 2011 The libmount & libblkid ----------------------- Both of the libraries can be debugged by setting an environment variable consisting of a number. The number will be used as a bit mask, so the more 1 the higher the debugging level. Search for `DEBUG' from files libblkid/src/blkidP.h libmount/src/mountP.h to see what the different bits mean. At the time of writing this the following enabled full debug. export LIBBLKID_DEBUG=all export LIBMOUNT_DEBUG=all export LIBFDISK_DEBUG=all export LIBSMARTCOLS_DEBUG=all The libblkid reads by default /etc/blkid.conf which can be overridden by the environment variable BLKID_CONF. See manual libblkid/libblkid.3 for details about the configuration file. Block device information is normally kept in a cache file (see blkid man page for more information about the cache file location) that can be overridden by the environment variable BLKID_FILE. To libmount uses three paths, which can be overridden by using environment variables. Notice that these environment variables are ignored for non-root users. env variable if not set defaults to LIBMOUNT_FSTAB /etc/fstab LIBMOUNT_MTAB /etc/mtab LIBMOUNT_UTAB /run/mount/utab or /dev/.mount/utab