From: Kern S. <ke...@si...> - 2006-11-30 15:10:22
|
On Wednesday 29 November 2006 22:34, Arno Lehmann wrote: > Hi, > > On 11/25/2006 11:06 AM, Kern Sibbald wrote: > > On Saturday 25 November 2006 00:36, Arno Lehmann wrote: > ... > > The problem with the output below is that the line numbers given in the dump > > do not correspond to 1.39.29 despite what the debug output indicates at the > > beginning. Something is wrong because the point at which it crashed does not > > correspond to anything reasonable, unless you had some sort of hardware > > memory fault, in which case, there isn't much Bacula can do. > > > > I recommend running a really comprehensive memory test on your machine. > > As I couldn't identify any problem by now, and I can't rule out an > individual problem (the autochanger problem might have been the result > of a not reproduceable hardware / memory problem) I think it's safe to > say I encountered a single hardware error. > > That I reported this as a possible Bacula bug tells something about my > high trust into the developers, right? It's not that I would usually > report such single failures in other software... Yes, of course, I would like to see every Seg Fault dump that is produced. 99.9% are due to something wrong in Bacula. In your case, I could not exclude a Bacula bug, but the dump was very bizarre leading me to think it might be a one shot thing as you note. > > Arno > > -- > IT-Service Lehmann al...@it... > Arno Lehmann http://www.its-lehmann.de > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share your > opinions on IT & business topics through brief surveys - and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > _______________________________________________ > Bacula-devel mailing list > Bac...@li... > https://lists.sourceforge.net/lists/listinfo/bacula-devel > |