Alastair McKinstry: Bringing the Brompton to the UK
read more »
--3177-- VALGRIND INTERNAL ERROR: Valgrind received a signal 11 (SIGSEGV) - exiting --3177-- si_code=80; Faulting address: 0x0; sp: 0x402A9FD40 valgrind: the 'impossible' happened: Killed by fatal signal ==3177== at 0x3801FDEA: unlinkBlock (m_mallocfree.c:190) ==3177== by 0x38020CAE: vgPlain_arena_malloc (m_mallocfree.c:1055) ==3177== by 0x38035516: vgPlain_cli_malloc (replacemalloc_core.c:101) ==3177== by 0x380022F5: vgMemCheck_malloc (mc_malloc_wrappers.c:182) ==3177== by 0x38035BA7: do_client_request (scheduler.c:1158) ==3177== by 0x380372B1: vgPlain_scheduler (scheduler.c:869) ==3177== by 0x38051B59: run_a_thread_NORETURN (syswrap-linux.c:87)This code has already killed one debugger (Intel DB) and sent strace into an infinite loop of segfaults. <Sigh />.
"Are you saved ?" "yes" "Are you prepared to die ?"The Night Sessions, Ken MacLeod's latest novel is set in the near future, after the "faith" (or oil) wars, when religion is barely tolerated by political society, distained and tainted; and the police and state have a policy of 'official non-cognisance' of religious activities. It's a police thriller, where the victims are, apparently, being killed for their religious beliefs.
Marc, from my experience, there is no 'secret' in the console-tools/kbd migration work. Just low involvment of all parties.
I have watched the work on console handling stuff in Debian for a few years now, and my conclusion is just that nearly nobody cares about it now.
I do maintain console-data that provides console fonts and keymaps. I took it over slowly from Alastair McKinstry (the console-tools maintainer mentioned in Marc's blog entry) because that involved maintaining localization of keymap names....that are used and visible in the installer.
Ideas to switch the installer to console-setup and related tools are floating around. Just not achieved...because of lack of motivated manpower. Progress was made because of Anton Zinoviev and Colin Watson's work, but the project is currently hosed on a quite critical choice:
#include <stdio.h>
#include <sys/types.h>
int main(int argc, char *argv[])
#ifdef LITTLE_ENDIAN
printf("Little Endian defined\n");
#endif
On Linux/x86, this prints outputs little-endian. Unfortunately it also does so on the IBM BlueGene (Linux, GNU Libc), which is,
by default, big-endian.
(Thanks to my colleague Honore Tapamo for discovering this).
It turns out that this is due to <sys/types.h> including <endian.h>, which has:
#define __LITTLE_ENDIAN 1234 #define __BIG_ENDIAN 4321 #define __PDP_ENDIAN 3412 /* This file defines __BYTE_ORDER' for the particular machine. */ #include <bits/endian.h> #ifdef __USE_BSD # define LITTLE_ENDIAN __LITTLE_ENDIAN # define BIG_ENDIAN __BIG_ENDIAN # define PDP_ENDIAN __PDP_ENDIAN # define BYTE_ORDER __BYTE_ORDER #endif #if __BYTE_ORDER == __LITTLE_ENDIAN # define __LONG_LONG_PAIR(HI, LO) LO, HI #elif __BYTE_ORDER == __BIG_ENDIAN # define __LONG_LONG_PAIR(HI, LO) HI, LO #endifWe're working on a code at the moment that has LITTLE_ENDIAN defined in Makefiles on Little-Endian architectures. This all needs to be changed to something like IS_LITTLE_ENDIAN to avoid this issue. POSIX requires that all symbols beginning with an underscore, followed by a Capital letter or another underscore, are reserved for "the system". Unfortunately the reverse does not appear to be true, and this then is a collision with a symbol that programmers thought was unique to the code being defined in system headers but with different meaning. Is there a standard for detecting byte order? There doesn't appear to be in POSIX. Linux / libc provides __BYTE_ORDER but what other Operating Systems does this work on ?
Abstract: Despite a fainter Sun, the surface of the early Earth was mostly ice-free. Proposed solutions to this so-called "faint young Sun problem" have usually involved higher amounts of greenhouse gases than present in the modern-day atmosphere. However, geological evidence seemed to indicate that the atmospheric CO2 concentrations during the Archaean and Proterozoic were far too low to keep the surface from freezing. With a radiative-convective model including new, updated thermal absorption coefficients, we found that the amount of CO2 necessary to obtain 273 K at the surface is reduced up to an order of magnitude compared to previous studies. For the late Archaean and early Proterozoic period of the Earth, we calculate that CO2 partial pressures of only about 2.9 mb are required to keep its surface from freezing which is compatible with the amount inferred from sediment studies. This conclusion was not significantly changed when we varied model parameters such as relative humidity or surface albedo, obtaining CO2 partial pressures for the late Archaean between 1.5 and 5.5 mb. Thus, the contradiction between sediment data and model results disappears.The suspected composition of the eary Earth (the Archean, when life is believed to have started, 3.8 to 2.5 billion years ago), has alternated between CO2 and other reducing gases, such as methane. Originally CO2 was thought to be the main greenhouse gas, making life possible. However the high CO2 levels required were a problem; high CO2 levels would have created siderite (FeCO3) in the top layers of soil as iron interacted with CO2 in the oxygen-free air. Since then methane has top billing as the greenhouse gas responsible, with significant hydrogen levels a possibility. Over time, methane has come out on top. And thats what I wrote when I did my literature review for my PhD. Now I'm tidying it up a bit, and that section may be in for a rewrite. But what does it mean for our Climate change models of today?
... scanning lib[10].a ... scanning lib[11].a ... scanning lib[12].a ... scanning lib[13].a ... scanning lib[14].a ... scanning lib[15].a ... pgf90 -Wl,--start-group ./master.o -L. -l[1] -l[2] -l[3] -l[4] -l[5] -l[6] -l[7] -l[8] -l[9] -l[10] -l[11] -l[12] -l[13] -l[14] -l[15] -Wl,--end-group -llapack -lblas ./lib[2].a(cprep1.o)(.text+0x181d): In function cprep1': ...Next time, think of someone trying to find these interesting files. People using regexps, ok ? What do these 'libraries' contain, anyway ?
subroutine funmame( param1, param2, param3, #ifdef FOO32 foo, bar, #endif param7, param8, #include "basarg.h" )Remarkably, basarg.h included:
C Comment.
param5, param6,
#ifdef SOMETHING
param10, param20,
#endif
There were in fact dozens of parameters in basarg.h.. And even a higher.h that
included basarg.h but had more parameters ...
#ifdef DOC C Some fortran comments. C Yes, ordinary comments, nothing fancy like preprocessor directives, but if you want C your code without a paragraph explaining what it does, you can just preprocess it C and remove it. C C Perhaps they'd expected that their fellow developers would write essays in the C source code that would make it hard to follow, but then, you'd still need to edit C the full source code to debug and develop it, right? C #endif
Cormac and Caoimhe at a patisserie with Chocolate lion in Concarneau, Brittany
Next.