Welcome to the Reiser4 Wiki, the Wiki for users and developers of the ReiserFS and Reiser4 filesystems.

For now, most of the documentation is just a snapshot of the old Namesys site (archive.org, 2007-09-29).

There was also a Reiser4 Wiki (archive.org, 2007-07-06) once on pub.namesys.com.

Debug Reiser4progs

From Reiser4 FS Wiki
(Difference between revisions)
Jump to: navigation, search
(Added Debug_Reiser4progs page)
 
(Root permissions are not needed to perform make in reiser4progs.)
 
(2 intermediate revisions by 2 users not shown)
Line 1: Line 1:
 
= Debug Reiser4progs with GDB =
 
= Debug Reiser4progs with GDB =
  
1. Make sure you have the latest version of Reiser4progs:
+
1. Make sure you have the latest version of [[Reiser4progs]]:
  
 
     $ git clone https://github.com/edward6/reiser4progs
 
     $ git clone https://github.com/edward6/reiser4progs
Line 18: Line 18:
 
Possible solution:
 
Possible solution:
  
     # cd /usr/lib64
+
     $ cd /usr/lib64
     # mv libuuid.so libuuid.so_
+
     $ sudo mv libuuid.so libuuid.so_
     # ln -s libossp-uuid.so libuuid.so
+
     $ sudo ln -s libossp-uuid.so libuuid.so
  
 
3. Run gdb against needed binary that can be found in ./progs directory. For example:
 
3. Run gdb against needed binary that can be found in ./progs directory. For example:
  
     # gdb progs/fsck/fsck.reiser4
+
     $ gdb progs/fsck/fsck.reiser4
 +
 
 +
[[category:Reiser4]]

Latest revision as of 14:10, 25 June 2017

[edit] Debug Reiser4progs with GDB

1. Make sure you have the latest version of Reiser4progs:

   $ git clone https://github.com/edward6/reiser4progs

2. Compile and build static binaries with debugging symbols:

   $ cd reiser4progs
   $ ./prepare
   $ ./configure --enable-debug --enable-full-static
   $ make

Troubleshooting. If you use Fedora distro, then make command can fail with the following:

    /usr/bin/ld: cannot find -luuid" during compilation

Possible solution:

   $ cd /usr/lib64
   $ sudo mv libuuid.so libuuid.so_
   $ sudo ln -s libossp-uuid.so libuuid.so

3. Run gdb against needed binary that can be found in ./progs directory. For example:

   $ gdb progs/fsck/fsck.reiser4
Personal tools