Coding Relic - Latest Comments

Re: The Control Plane is not an Aircraft

ks7000 — Sun, 27 Aug 2017 16:17:59 -0000

Now I know something about CompactPCI cards, that MicroSwitch is very useful!

Re: Code Snippet: SO_BINDTODEVICE

ks7000 — Thu, 24 Aug 2017 20:41:09 -0000

I am studying "fping" and SO_BINDTODEVICE is necessary with "-I" option; thanks for this note!

Re: Coding Relic: Software Engineering Maxim #8: Money is not the only motivator

DGentry — Thu, 13 Jul 2017 09:40:54 -0000

Doubtful.

Re: Coding Relic: Software Engineering Maxim #8: Money is not the only motivator

Mark Essel — Thu, 13 Jul 2017 04:44:39 -0000

Will we ever learn which maxims may be true?

Re: Coding Relic: Software Engineering Maxim #1: Small teams are bigger than large teams

Oleg Mihailik — Sun, 25 Jun 2017 18:22:18 -0000

Whereas dwarves+Gandalf+Hobbit clearly were too many, and the when going together they always ended up in a pickle.

Re: Coding Relic: Software Engineering Maxim #1: Small teams are bigger than large teams

Oleg Mihailik — Sun, 25 Jun 2017 18:17:23 -0000

That is why Friends always had guest stars: 4 is not enough.
And The Big Bang Theory could go on without Kripke or Prof. Proton for arbitrary time.

Re: Stackoverflow Maintenance Page

Mujahed Akas — Sat, 05 Dec 2015 08:56:45 -0000

Is there any way, we can access stackoverflow during maintenncae?

Re: gdb lies to you

why bother — Thu, 22 Oct 2015 20:36:36 -0000

I just ran into the same issue. Unfortunately the part of code I need to debug is where the call stack gets mixed up parameters. Took me awhile to notice a scalar parameter was shown as the value of an address, some huge number. I'm running on a Ubuntu vm with X86_64. The same program built on a x86_64 Fedora works like a charm. BT shows the arguments are consistent. My application is to produce HMAC SHA-1 values and compare with expected values. The test on one blob of data works and fails on the other bob. I used gdb to dump the binary just to be sure it was not corrupted. It wasn't. I'm thinking of an alternative. It's not a huge problem but I like all mysteries solved.

Re: Ode to Enum

Janus Troelsen — Thu, 27 Aug 2015 11:13:56 -0000

"I've put it on my list of things to research and write about" Did you progress on this?

Re: The Six Million Dollar LibC

LafayetteCoboll — Thu, 02 Jul 2015 08:48:25 -0000

According to the Wikipedia page on the LGPL, if you link to an LGPL library dynamically, you are fine. If you link statically you must provide all of your object files (or source code). I would think you would also have to provide your Makefile or equivalent as well, but that isn't mentioned.

Re: Coding Relic: certdata.txt

Fazal Majid — Thu, 04 Jun 2015 21:59:50 -0000

It looks like that CA bundle hasn't been updated since 2012. The current latest one from their Mercurial repo is here: https://hg.mozilla.org/proj...

Re: Privacy vs Voyeurism

Joseph — Thu, 28 May 2015 06:56:00 -0000

Ranging over a rich variety of material from film and film literature,
and encompassing a critical interrogation of traditional realist
ethnographic and cinematic texts, this book highlights the extent to
which the cinema has contributed to the rise of voyeurism throughout
society. The cinema not only turns its audience into voyeurs, eagerly
following the lives of its screen characters, but casts its key players
as onlookers, spying on other's lives. The nature of the cinematic
voyeur is examined in depth, as are its implications for contemporary
society. Norman K Denzin analyzes Hollywood's manipulations of gender,
race and class, and, drawing on the work of Foucault, argues that the
cinematic gaze must be understood as part of the machinery of
surveillance and power which regulates social behaviour in the late
twentieth century.

Re: Coding Relic: Code Snippet: libarchive

Vladislav Koshyl — Tue, 24 Feb 2015 06:48:20 -0000

Hi, dude. Very good article, but I haven't seen anything about sets passwords to archives. I'm use this code, but nothing works:

ArchiveWrite &archWrite; - input argument
archWrite.Arch = ArchiveWriteUnique(archive_write_new());
ret = archive_write_set_passphrase(archWrite.Arch.get(), "123456");

Password isn't created. What I'm doing wrong?

Re: Coding Relic: ATA Commands in Python

dragosmc — Wed, 04 Feb 2015 15:30:33 -0000

DGentry I have tried your example code and it works fine on internal HDDs (connected through a SATA cable), but I was unsuccessful running it on a USB connected HDD via a SATA-to-USB adapter. It seems that the operation code is invalid. Any thoughts on this ? Anyway, thanks for the code :)

Re: Coding Relic: Listing Processes with libproc

vyom — Mon, 05 Jan 2015 04:27:42 -0000

good, this is one place, where I could see a full working example! thanks.

Re: gdb lies to you

alb3rtobrr — Fri, 28 Nov 2014 05:25:41 -0000

Thanks a lot for the info! Although you wrote this post more than 6 years ago it has been really interesting to read it and confirm what I was suspecting about gdb: he is a liar!! :P

Re: Code Snippet: SO_BINDTODEVICE

krishna — Thu, 20 Nov 2014 20:16:22 -0000

After bind and issuing the setsockopt ,What happens if the interface is deleted and recreated wit the same name?? (In case of dynamic interfaces like IPIP interfaces )
Can I read and write data from/to the socket fd ?

Re: Coding Relic: Listing Processes with libproc

jared — Tue, 18 Nov 2014 09:48:50 -0000

thanks for the info on pcpu

Re: The Six Million Dollar LibC

jujodi — Sat, 08 Nov 2014 21:50:38 -0000

How can I use Bionic's OpenSSL to create a SHA256. There is no #include <openssl sha.h="">

Re: Ode to Enum

frank — Mon, 13 Oct 2014 08:33:54 -0000

I also like enums because they are easy maintainable.

Example:

Before inserting a new operation:

typedef enum {
OP_FOO,
OP_BAR,
OP_MAX, // gives the no. of operations
} operation_t;

After t inserting the new operation:

typedef enum {
OP_FOO,
OP_NEW, // new operation inserted
OP_BAR,
OP_MAX, // no. of operations is automatically adjusted
} operation_t;

If OP_MAX is used e.g. to define the size of an array, its is automatically updated, too.
If you do this with #defines, you always have to modify the file in different places:

- adding the new define
- adjusting all the following defines
- adjusting the no. of defines

Re: Soft Errors Are Hard Problems

Olivier — Wed, 08 Oct 2014 19:29:28 -0000

Hi Baruch

The first step to take to understand the source of errors is try to get a physical bitmap of errors location in your DIMM and plot them on a relative map centered on the nearby bump (I'm assuming here that you are using flip chip package). This map of errors might tell you a lot about the origin of the errors. Keep in mind that alpha particles from natural radioisotopes won't travel beyond 100 microns. So you are correct, if alpha particles is the problem, they have to come from within the packaging. Check out the materials in the vicinity of the die. These materials can be tested individually in an alpha counter, that's usually how it's done.You'll have to talk to your package house and ask if they change material from one chip lot to the other since you're seeing chips with several errors and others that are error free. Try to track manufacturing lots as another clue. It is correct to state that testing the whole package for alpha particles emission won't help.
Cosmic ray (high energy neutrons) and thermal neutrons (only if there's abundance of Boron 10 in the die and packaging) are particles external to the chip. Don't worry about betas.

Olivier

Re: Soft Errors Are Hard Problems

DGentry — Tue, 07 Oct 2014 09:49:09 -0000

Alpha particles are so large that they tend not to penetrate well, so the packages of nearby chips will protect them from alpha particles emitted elsewhere within the room.

Beta particles (electrons) and cosmic rays can penetrate the package of chips, but those are from the solar wind not radioactive decay of anything local.

I'm not sure that a radiation counter will detect alpha particles from the packaging materials. The situation I've seen is with the bonding agent emitting alpha particles, which is a "goo" inside the package which cushions the die and the wires between the silicon die and the pins on the package. The particles which hit the silicon die can cause errors, while the plastic of the package surrounding the goo would tend to absorb the rest.

Re: Soft Errors Are Hard Problems

Baruch Even — Tue, 07 Oct 2014 04:24:23 -0000

I see plenty of soft errors in DIMMs and PCIe devices. The distribution is such that some components see no soft errors and others are seeing plenty. I believe that the external forces (various particles) are not even remotely relevant and it points me more to faulty devices.

The theory of radioactive components is super interesting in that regard and I'm wondering if there is a way to check for it. What sort of options do I have to monitor for radioactive emissions in devices? Will they mean much if I can only test outside the cases, besides the racks? Are the failures expected to happen in the device with the problematic compound or will it affect (more weakly) nearby devices as well?

Just noticed the article is 5 years old... doh. I still wonder about my above questions if you care to think about that.

Re: Coding Relic: ATA Commands in Python

Ibad Khan — Fri, 22 Aug 2014 12:33:20 -0000

If you abandoned this approach what was the later approach? Considering I want to use Python and not to run as root.

Re: Coding Relic: Code Snippet: libarchive

SITA J — Tue, 17 Jun 2014 06:25:15 -0000

Using above code for Reading File Contents I could read contents of files within rar and tar archives into a buffer but not zip i.e it gives negative number of bytes read.