emo/procps
1
0
Fork 0
Code Issues Pull Requests Packages Releases Activity

sync BUGS w/ Makefile

Browse Source
This commit is contained in:
albert 2004-10-20 00:12:12 +00:00
parent d89cf44470
commit 22d06af53c
1 changed files with 6 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
BUGS
View File

@ -15,7 +15,7 @@ Send comments, bug reports, patches, etc., to albert@users.sf.net
What to send What to send
============ ============
It is much more useful to me if a program really crashes to recompile it It is much more useful to me if a program really crashes to recompile it
with make "CC=gcc -ggdb -O", run it with "gdb prog" and "run" and send with make "CFLAGS=-ggdb -O", run it with "gdb prog" and "run" and send
me a stack trace ('bt' command). That said, any bug report is still me a stack trace ('bt' command). That said, any bug report is still
better than none. better than none.
@ -24,15 +24,13 @@ strace and ltrace output are very helpful:
strace -o output-file ps --blah strace -o output-file ps --blah
bzip2 output-file bzip2 output-file
It might be nice to get rid of miscellaneous compiler warnings, but I also like "ps --info" output, even if there isn't a ps problem.
don't bend over backwards to do it.
Kernel-Dependent Patches Kernel-Dependent Patches
======================== ========================
If you send me patches which are specific to *running* with a particular If you send me patches which are specific to *running* with a particular
kernel version of /proc, please condition them with the runtime determined kernel version of /proc, please condition them with the runtime determined
variable `linux_version_code' from libproc/kvers.c. It is the same variable 'linux_version_code' from libproc/version.c. It is the same
number as the macro LINUX_VERSION_CODE for which the kernel /proc fs number as the macro LINUX_VERSION_CODE for which the kernel /proc fs
code was compiled. code was compiled.
@ -56,6 +54,9 @@ to create your diffs and you will make me happy. Also make sure to
include a description of what the diff is for or I'm likely to ignore include a description of what the diff is for or I'm likely to ignore
it because of general lack of time... it because of general lack of time...
It might be nice to get rid of miscellaneous compiler warnings, but
don't bend over backwards to do it.
Code Structure Code Structure
============== ==============