All of the interesting technological, artistic or just plain fun subjects I'd investigate if I had an infinite number of lifetimes. In other words, a dumping ground...
Thursday, 25 February 2010
Thursday, 18 February 2010
Clojure & QT
http://lifeofaprogrammergeek.blogspot.com/2009/05/model-view-controller-gui-in-clojure.html
http://dist.trolltech.com/developer/download/webstart/
http://en.wikibooks.org/wiki/Clojure_Programming
http://technotales.wordpress.com/2007/10/03/like-slime-for-vim/
http://tealeg.blogspot.com/2008/11/on-clojure-part-3-designer-uis-and.html
http://briancarper.net/blog/clojure-qt4-memory-leaks
http://briancarper.net/blog/clojure-qt4-system-tray-mail-checker
http://doc.trolltech.com/qtjambi-4.4/html/com/trolltech/qt/qtjambi-index.html
http://briancarper.net/blog/qt4-in-lisp
http://kevinoncode.blogspot.com/2009/01/creating-clojure-gui-application-with.html
http://dist.trolltech.com/developer/download/webstart/
http://en.wikibooks.org/wiki/Clojure_Programming
http://technotales.wordpress.com/2007/10/03/like-slime-for-vim/
http://tealeg.blogspot.com/2008/11/on-clojure-part-3-designer-uis-and.html
http://briancarper.net/blog/clojure-qt4-memory-leaks
http://briancarper.net/blog/clojure-qt4-system-tray-mail-checker
http://doc.trolltech.com/qtjambi-4.4/html/com/trolltech/qt/qtjambi-index.html
http://briancarper.net/blog/qt4-in-lisp
http://kevinoncode.blogspot.com/2009/01/creating-clojure-gui-application-with.html
Wednesday, 17 February 2010
Friday, 5 February 2010
Linux glibc Heap Consistency Checking
Heap Consistency Checking
Another possibility to check for and guard against bugs in the use of
malloc
, realloc
and free
is to set the environment variable MALLOC_CHECK_
. When MALLOC_CHECK_
is set, a special (less efficient) implementation is used which is designed to be tolerant against simple errors, such as double calls of free
with the same argument, or overruns of a single byte (off-by-one bugs). Not all such errors can be protected against, however, and memory leaks can result. If MALLOC_CHECK_
is set to 0
, any detected heap corruption is silently ignored; if set to 1
, a diagnostic is printed on stderr
; if set to 2
, abort
is called immediately. This can be useful because otherwise a crash may happen much later, and the true cause for the problem is then very hard to track down. Thursday, 4 February 2010
Changing shared memory size on Linux
This is useful for Postgresql and Oracle.
Look in to sysctl.
Here is a sample /etc/sysctl.conf file.
[@ ~]# cat /etc/sysctl.conf
# Kernel sysctl configuration file for Red Hat Linux
#
# For binary values, 0 is disabled, 1 is enabled. See sysctl(8) and
# sysctl.conf(5) for more details.
# Controls IP packet forwarding
net.ipv4.ip_forward = 0
# Controls source route verification
net.ipv4.conf.default.rp_filter = 1
# Do not accept source routing
net.ipv4.conf.default.accept_source_route = 0
# Controls the System Request debugging functionality of the kernel
kernel.sysrq = 1
# Controls whether core dumps will append the PID to the core filename.
# Useful for debugging multi-threaded applications.
kernel.core_uses_pid = 1
# Controls the maximum size of a message, in bytes
kernel.msgmnb = 65536
# Controls the default maxmimum size of a mesage queue
kernel.msgmax = 65536
# Controls the maximum shared segment size, in bytes
kernel.shmmax = 4294967295
# Controls the maximum number of shared memory segments, in pages
kernel.shmall = 268435456
Subscribe to:
Posts (Atom)