These files contain loops that convert system data into python objects
and during the process they create objects and dereference their
refcounts after they have been added to the resulting list.

However, in case of errors during the creation of those python objects,
the refcount to previously allocated objects is dropped again with
Py_XDECREF, which should be a no-op in case the paramater is NULL. Even
so, in most of these loops the variables pointing to the objects are
never set to NULL, even after Py_DECREF is called at the end of the loop
iteration. This means, after the first iteration, if an error occurs
those python objects will get their refcount dropped two times,
resulting in a possible double-free.

In plain old C, variables shall be declared above

Fix #1606

* Fix nice() for realtime processes under Solaris 10

fixes #1194

* Use psinfo as fallback [gu]id source on Solaris 10

fixes #1193

* Fix double free

* Match ssize_t return type of read functions

* Fix undefined behavior

with respect to strict aliasing rules and fix some warnings

For example, under strict aliasing rules of the C standard, casting a
char pointer to a struct pointer and accessing the character array
through that struct pointer yields undefined behavior.

* Update HISTORY with Solaris notes

* Try to extract argv[] from process address space first

* Add comments and OOM exception

* Handle the case with empty array