June 29th, 2005

llewellyn

When the dog bites…

Which are a few of your favourite things?

Raindrops on roses
0(0.0%)
Whiskers on kittens
1(2.7%)
Bright copper kettles
0(0.0%)
Warm woollen mittens
0(0.0%)
Brown paper packages tied up with string,
1(2.7%)
Cream coloured ponies
0(0.0%)
Crisp apple strudel
1(2.7%)
Door bells
0(0.0%)
Sleigh bells
0(0.0%)
Schnitzel with noodles
0(0.0%)
Wild geese that fly with the moon on their wings,
0(0.0%)
Girls in white dresses and blue satin sashes
2(5.4%)
Snowflakes that stay on my nose and eye-lashes
1(2.7%)
Silver white winters that melt into spring
0(0.0%)
geeky

Error

I am consistently (but irregularly) irritated when I get errors or warnings to stderr that don't identify the process that they come from. I'd like some general sort of solution to this that I can implement and ignore.

My best thought so far is to use LD_PRELOAD to wrap fprintf such that outputs to stderr get [pid] prepended, but I suspect that this is insufficiently general; plus it is ick.

Any suggestions, anyone?