Re: Size of a kernel module is different at build place and after installation

2009-09-22 Thread sobtwmxt
Manoj Srivastava ieee.org> writes: > > As mentioned in another post in this thread, the installed > modules are stripped of debugging information. make-kpkg can now > create a linux-debug-** package that has detached debug information, to > be used for debugging, as needed. > >

Re: Size of a kernel module is different at build place and after installation

2009-09-22 Thread sobtwmxt
Emanoil Kotsev yahoo.com> writes: > > are you using the same filesystem on both (i.e. ext3)? > It is ext3 on both. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Size of a kernel module is different at build place and after installation

2009-09-21 Thread sobtwmxt
I have built a custom kernel, using make-kpgk, from debian source. Using ls -l, there is difference in the size of kernel modules, .ko files, at build place and after installation of the package. I only looked at 2 unrelated modules, but I think there will be a difference in the size of other

How to have gdb step into a function from the application's shared library?

2009-07-17 Thread sobtwmxt
Consider the following pseudo code: appLib.h int funcInAppLib(void); :: main.c :: #include "appLib.h" int main(void) { if (funcInAppLib() < 0) printf("funcInAppLib() < 0\n"); } Where the application is debianized, a