This page validates as XHTML 1.0, and will look much better in a browser that supports web standards, but it is accessible to any browser or Internet device. It was created using techniques detailed at glish.com/css/.
Saturday April 30, 2005 Finn, our youngest samoyed is huge compared to Cleo. She is nearly 18 months old and weighs about 35 lbs, he is 7 months old and is almost 60 lbs, will he ever stop growing? The vet has reminded us that puppies of large dogs must have their exercise limited to avoid joint problems in later life so he is limited to 30 minute walks.
Finn has had a problem ( I won't go into details but it is at the end without teeth!) which has been very uncomfortable for him. He hasn't been able to sleep for a couple of nights which has stopped me sleeping as well - it's just like having small children all over again. The vet has cured him with a very unpleasant procedure and some antibiotics and he is catching up with his sleep.
During the week I collected several escalations that required analysis of userland core files. In both cases I was supplied the core file and a showrev -p and asked for a quick analysis. So my choices were to either..
Point our jumpstart configuration scripts at the showrev-p output and install a machine so that I have all the right libraries in the right place. Machines are an expensive resource and it seems a waste to book and occupy a whole machine just for this.
Ask the customer for some more files from his machine. The binary that generated the core and then all the shared libraries listed in the output of pldd core. With those I can build a dbxrc that maps the loads of the libraries to use the customer's ones. Once I have these I can debug the core on any machine where dbx is available.
In solaris 10 coreadm gives you much better control over what parts of the faulting processes address space end up in the core file. The default will include the shared library segments so core files will be bigger but debugging them wont need all the other files.