My program core dumped but there was no core file. The problem was that the core file size was 0: $ ulimit -a core file size (blocks, -c... Use ulimit to enable it: $ sudo bash # ulimit -c unlimited

Summarized from The C Book : There are essentially two types of object in C: the internal and external objects. Anything declared outside a function is external; anything inside one, including its formal parameters, is internal. Since no function can be defined inside another, functions are always external. All function declarations implicitly have the extern keyword stuck in front of them, whether or not you put it there. These two declaearions are equivalent: void some_function(void); extern void some_func... The term linkage is used to describe the accessibility of objects from one file to another. There are three types of linkage: external , internal , and no linkage . Type of linkage Type of object Accessibility external external Across files, througout the program internal external Within...

When I ran this code snippet with strace : f = fopen("TZ", "rb"); fseek(f, 0, SEEK_END); ... I saw ENOTTY error with uClibc : open("TZ", O_RDONLY|O_LARGEFILE) = 3 ioc... With the normal gnu libc , there's no such error: open("TZ", O_RDONLY) = 3 fstat64... There was no error running the program. But for some reason, uClibc did a ioctl call when it opened a file, and handled it appropriately.

To diff two directories: diff dir1 dir2 To diff two directories recursively: diff -r dir1 dir2 Version of diff : $ diff -v diff (GNU diffutils) 2.8.1 Copyrig...

By default SELinux blocks execstack permission. According to Ulrich Drepper : "As the name suggests, this error is raised if a program tries to make its stack (or parts thereof) executable with an mprotect call. This should never, ever be necessary. Stack memory is not executable on most OSes these days and this won't change. Executable stack memory is one of the biggest security problems. An execstack error might in fact be most likely raised by malicious code." You can check if a library/application requires execstack by using the execstack utility: execstack -q PATHTOPROGRAM You can try to clean the flag and see if the application still runs: execstack -c PATHTOPROGRAM To allow execstack for cc1 : # grep cc1 /var/log/audit/audit.log | audit2allow ...

Sometimes you want to disable the UAC because a program written for XP doesn't have the notion of UAC. When running such a program under Windows 7, it silently denies your preference changes. Enter Control Panel, goto User (Account) Manager. Click the link "Change User Account Control Settings". Move the slider to the bottom

In the "Program search" (or Run) box, enter lusrmgr.msc to bring up the "Local Users and Groups" dialog. Double click the user name you want to set password never expire.

I built BartPE on a USB drive but it couldn't see the hard drives. Turned out I needed drivers for the SATA drives on my new PC. These were the steps: Extract/install the DriverPacks Base program to C:\DPsBase\ Download the latest Mass Storage DriverPack directly to the DriverPacks folder: C:\DPsBase\DriverPacks\ Run C:\DPsBase\DPs_BASE.exe Detailed instructions: http://driverpacks.net/docs/Miscellaneous%20guides/driverpacks-base-bartpe-guide

Two of the three PreparedStatement.setBinaryStream methods are not implemented as of version 9.0-801 of the PostgreSQL JDBC driver. Test program: import java.io.*; import java.sql.*; pub... Also note that setBinaryStream only works on a bytea column.