Know more about a process

Today, I would like to introduce some ways to get more information of a process, and hope those can help in trouble-shooting and debugging.

List environment variables

To list the environment variables of a process you can issue the command:
ps ewww pid
E.g.:

ahlam@oxygen:~/test/malloc$ ps ewww 4752
PID TTY      STAT   TIME COMMAND
4752 pts/2    Ss+    0:00 bash USER=ahlam HOME=/home/ahlam DESKTOP_SESSION=default GDM_XSERVER_LOCATION=loca
l GTK_IM_MODULE=gcin LOGNAME=ahlam USERNAME=ahlam GDM_LANG=en_HK.UTF-8 PATH=/usr/local/sbin:/usr/local/bin:/u
sr/sbin:/usr/bin:/sbin:/bin:/usr/bin/X11:/usr/games DISPLAY=:0.0 LANG=en_HK.UTF-8 XMODIFIERS=@im=gcin XAUTHOR
ITY=/home/ahlam/.Xauthority SHELL=/bin/bash GDMSESSION=default QT_IM_MODULE=gcin PWD=/home/ahlam SSH_AUTH_SOC
K=/tmp/ssh-nRdglP4521/agent.4521 SSH_AGENT_PID=4563 DBUS_SESSION_BUS_ADDRESS=unix:abstract=/tmp/dbus-ix9My5o6
DJ,guid=8abd2646dc897f03d1cfb07e3a3d4b00 GTK_RC_FILES=/etc/gtk/gtkrc:/home/ahlam/.gtkrc-1.2-gnome2 SESSION_MA
NAGER=local/oxygen:/tmp/.ICE-unix/4521 GNOME_KEYRING_SOCKET=/tmp/keyring-fXmYul/socket GNOME_DESKTOP_SESSION_
ID=Default TERM=xterm COLORTERM=gnome-terminal WINDOWID=31457489

List out the threads of a process

ps ms pid
E.g:

ahlam@oxygen:~/test/malloc$ ps ms 4752
UID   PID          PENDING          BLOCKED          IGNORED           CAUGHT STAT TTY        TIME COMMAND
1000  4752 0000000000000000                -                -                - -    pts/2      0:00 bash
1000     - 0000000000000000 0000000000000000 0000000000384004 000000004b813efb Ss+  -          0:00 -

Print the memory map

To list the memory map of a process, you can use the pmap command. It lists out the mapped memory regions and the purpose of the memory regions. It also lists out the .so files loaded by the process.
pmap pid
E.g:

ahlam@oxygen:~/test/malloc$ pmap 4752
4752:   bash
08048000    644K r-x--  /bin/bash
080e9000     20K rw---  /bin/bash
080ee000   1804K rw---    [ anon ]
b7c94000     36K r-x--  /lib/tls/i686/cmov/libnss_files-2.4.so
b7c9d000      8K rw---  /lib/tls/i686/cmov/libnss_files-2.4.so
b7c9f000     32K r-x--  /lib/tls/i686/cmov/libnss_nis-2.4.so
b7ca7000      8K rw---  /lib/tls/i686/cmov/libnss_nis-2.4.so
b7ca9000     72K r-x--  /lib/tls/i686/cmov/libnsl-2.4.so
b7cbb000      8K rw---  /lib/tls/i686/cmov/libnsl-2.4.so
b7cbd000      8K rw---    [ anon ]
b7cbf000     28K r-x--  /lib/tls/i686/cmov/libnss_compat-2.4.so
b7cc6000      8K rw---  /lib/tls/i686/cmov/libnss_compat-2.4.so
b7cd7000    204K r----  /usr/lib/locale/en_HK.utf8/LC_CTYPE
b7d0a000      4K r----  /usr/lib/locale/en_HK.utf8/LC_NUMERIC
b7d0b000      4K r----  /usr/lib/locale/en_HK.utf8/LC_TIME
b7d0c000    860K r----  /usr/lib/locale/en_HK.utf8/LC_COLLATE
b7de3000      8K rw---    [ anon ]
b7de5000   1204K r-x--  /lib/tls/i686/cmov/libc-2.4.so
b7f12000      8K r----  /lib/tls/i686/cmov/libc-2.4.so
b7f14000      8K rw---  /lib/tls/i686/cmov/libc-2.4.so
b7f16000     12K rw---    [ anon ]
b7f19000      8K r-x--  /lib/tls/i686/cmov/libdl-2.4.so
b7f1b000      8K rw---  /lib/tls/i686/cmov/libdl-2.4.so
b7f1d000    220K r-x--  /lib/libncurses.so.5.5
b7f54000     32K rw---  /lib/libncurses.so.5.5
b7f5c000      4K rw---    [ anon ]
b7f5d000      4K r----  /usr/lib/locale/en_HK.utf8/LC_MONETARY
b7f5e000      4K r----  /usr/lib/locale/en_HK.utf8/LC_MESSAGES/SYS_LC_MESSAGES
b7f5f000      4K r----  /usr/lib/locale/en_HK.utf8/LC_PAPER
b7f60000      4K r----  /usr/lib/locale/en_HK.utf8/LC_NAME
b7f61000      4K r----  /usr/lib/locale/en_HK.utf8/LC_ADDRESS
b7f62000      4K r----  /usr/lib/locale/en_HK.utf8/LC_TELEPHONE
b7f63000      4K r----  /usr/lib/locale/en_HK.utf8/LC_MEASUREMENT
b7f64000     28K r--s-  /usr/lib/gconv/gconv-modules.cache
b7f6b000      4K r----  /usr/lib/locale/en_HK.utf8/LC_IDENTIFICATION
b7f6c000      8K rw---    [ anon ]
b7f6e000    100K r-x--  /lib/ld-2.4.so
b7f87000      8K rw---  /lib/ld-2.4.so
bfa1c000     88K rw---    [ stack ]
ffffe000      4K -----    [ anon ]
total     5528K

/proc/pid

In proc/pid directory, it contains much information of a process.

ahlam@oxygen:~/test/malloc$ ls -l /proc/4752
total 0
dr-xr-xr-x 2 ahlam ahlam 0 2007-04-19 20:17 attr
-r-------- 1 ahlam ahlam 0 2007-04-19 20:17 auxv
-r--r--r-- 1 ahlam ahlam 0 2007-04-19 19:57 cmdline
-r--r--r-- 1 ahlam ahlam 0 2007-04-19 20:17 cpuset
lrwxrwxrwx 1 ahlam ahlam 0 2007-04-19 18:20 cwd -> /home/ahlam/test/malloc
-r-------- 1 ahlam ahlam 0 2007-04-19 19:58 environ
lrwxrwxrwx 1 ahlam ahlam 0 2007-04-19 20:17 exe -> /bin/bash
dr-x------ 2 ahlam ahlam 0 2007-04-19 19:57 fd
-r--r--r-- 1 ahlam ahlam 0 2007-04-19 20:06 maps
-rw------- 1 ahlam ahlam 0 2007-04-19 20:17 mem
-r--r--r-- 1 ahlam ahlam 0 2007-04-19 20:17 mounts
-r-------- 1 ahlam ahlam 0 2007-04-19 20:17 mountstats
-rw-r--r-- 1 ahlam ahlam 0 2007-04-19 20:17 oom_adj
-r--r--r-- 1 ahlam ahlam 0 2007-04-19 20:17 oom_score
lrwxrwxrwx 1 ahlam ahlam 0 2007-04-19 20:17 root -> /
-rw------- 1 ahlam ahlam 0 2007-04-19 20:17 seccomp
-r--r--r-- 1 ahlam ahlam 0 2007-04-19 20:17 smaps
-r--r--r-- 1 ahlam ahlam 0 2007-04-19 19:57 stat
-r--r--r-- 1 ahlam ahlam 0 2007-04-19 20:17 statm
-r--r--r-- 1 ahlam ahlam 0 2007-04-19 19:57 status
dr-xr-xr-x 3 ahlam ahlam 0 2007-04-19 20:17 task
-r--r--r-- 1 ahlam ahlam 0 2007-04-19 20:17 wchan

For details, please man proc.

Optimistic memory allocation strategy in Linux

If you know C programming language, you must know what is malloc. malloc is for dynamic memory allocation. In colleges, we learned that malloc should return NULL in case of out-of-memory. However, it is not the case in Linux. By default, Linux uses optimistic memory allocation strategy. Under this strategy, Linux assumes there always exists free memory. The memory region returns by malloc is not actually allocated until the process touches the memory region. This means the memory region returns by malloc may not be available. In case of out-of-memory, the OOM Killer in Linux will pick up one or more process to kill. This sounds strange!

Reference:
man malloc
http://linux-mm.org/OOM_Killer

Change the title of xterm

In most modern Linux distribution, the title of terminal follows the working directory. The mechanism behind this feature is not simple. You can even customize the title. Please note that, in this article, it is assumed to use xterm and bash.

In xterm, the following escape sequence can change the title of terminal windows:

ESC]0;title_stringBEL

where ESC and BEL is 033 and 007 (in octal ASCII) respectively. For example, we can use the following echo command to set the terminal title as "Hello World.":

echo -ne "\033]0;Hello World.\007"

However, if you issue the above command in your terminal, the title may not be changed. It is because the PROMPT_COMMAND environment variable have already been defined for changing the terminal title. The value in PROMPT_COMMAND environment variable will be executed as command prior to issuing each prompt. In my terminal, the value of PROMPT_COMMAND is:

echo -ne "\033]0;${USER}@${HOSTNAME}: ${PWD/$HOME/~}\007"

In the above command, ${USER} and ${HOSTNAME} is the username and hostname respectively, while the ${PWD/$HOME/~} is the current working directory with $HOME abbreviated as ~. Therefore, in my terminal, the title will be changed to show username, hostname and current working directory, e.g.:

ahlam@oxygen: ~/download

To customize your terminal title, you should update the value of PROMPT_COMMAND, e.g.:

export PROMPT_COMMAND='echo -ne "\033]0;Hello World.\007"'

Reference:
How to change the title of an xterm
man bash

Adobe Reader crashes with SCIM

I am using Ubuntu 6.10. Recently, I have installed Adobe Reader 7.0.9. However, Adobe Reader crashed at startup. In ubuntuguide.org , it mentions Adobe Reader won't work with SCIM. Finally, I found the solution -- scim bridge. To solve the problem, install the scim-bridge package and edit the "acroread" script to insert the line "GTK_IM_MODULE=scim-bridge" at the beginning of the script, like:

#!/bin/sh
#

GTK_IM_MODULE=scim-bridge
...

Then, Adobe Reader launches normally!

Be careful with STL strings

Please refer to the following C++ code fragment:

    char charArray[4]={'a','b','c',0,};
    string str1(charArray);
    string str2;
    str2.append(charArray, 4);

Use the following lines to print out the contents of str1 and str2:

    cout << "str1 [" << str1 << ']' << endl;
    cout << "str2 [" << str2 << ']' << endl;

The output would be:

str1 [abc]
str2 [abc]

Two strings looks same. However, does str1 equal to str2?

    cout << (str1 == str2? "equal" : "not equal") << endl;

The output:

not equal

Why not!? Let's print out the size of the strings:

    cout << "str1 size = " << str1.size() << endl;
    cout << "str2 size = " << str2.size() << endl;

The output:

str1 size = 3
str2 size = 4

In short, we should be careful about the == operator of strings. It does not only compare the contents of strings, but it also compares the size of strings.

Does it really need to Lock?

In multi-threading environment, we always face the problem of race condition -- concurrent accessing sharing data among threads. To solve the problem, we can use locking primitives, e.g. mutex, to avoid concurrent accessing of sharing data. However, those locking primitives are expensive, since they involve system calls. In some cases, we can avoid using locks.

Counting
Suppose threads updating a count variable concurrently. To avoid race condition, I saw some implementation like:

mutex.lock();
count++;
mutex.unlock();

Increment an integer just takes one CPU instruction, but locking and unlocking of mutex takes hundreds or thousands of CPU instructions. To avoid race condition, we can use atomic operations provided by CPU. Referring to /usr/include/asm-i386, there is implementation of atomic add:

static __inline__ void atomic_add(int i, atomic_t *v)
{
__asm__ __volatile__(
LOCK_PREFIX "addl %1,%0"
:"=m" (v->counter)
:"ir" (i), "m" (v->counter));
}

In Apache Portable Runtime project, it provides a set of atomic operations for different platforms.

Circular Buffers
In general, without locking, a circular buffer cannot be thread-safe. However, under a restricted condition and implementation, there would be no race condition problem. In short, for a fixed size circular buffer, if there is exactly one reader and one writer, it does not need locking. It is because the reader only updates the read-pointer and the writer only updates the write-pointer. This issue have been discussed in http://ddj.com/dept/cpp/184401814.

Is Port 25 blocked?

Port 25, default port of SMTP, is for E-mail transferring. To reduce SPAM, ISPs normally block this port, especially for those household DSL accounts. Therefore, people may think that it is impossible to setup E-mail server at home.
I have experiences of using HKBN and Netvigator, they are not really block all port 25 traffics. They only block outgoing traffics, but not incoming traffic. To setup the E-mail server, we can use the "smarthost" trick.