object oriented programming vs debug oriented programing (Ex: debugging dm code with kgdb)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Are the devlopers of the device mapping code awair
of how difficult they are making debugging of the
code with kgdb?

Doing object programing like style programming in
C has a major downside. Code that manages the
struct dm_table is in dm_table.c and thus code
in dm_ioctl.c can mess with the structure. 

Unfortunately when useing kgdb on the code you
can see the struct dm_table stuff via pointers
becasue struct dm_table has been declared as
an empty structure.

It would be very helpfull for kgdb users if the
declaration of dm_table was made in dm.h, at least
for KGDB kernels, just to make the code easier to
follow with kgdb.

-piet

--
dm-devel mailing list
dm-devel@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/dm-devel

[Index of Archives]     [DM Crypt]     [Fedora Desktop]     [ATA RAID]     [Fedora Marketing]     [Fedora Packaging]     [Fedora SELinux]     [Yosemite Discussion]     [KDE Users]     [Fedora Docs]

  Powered by Linux