>>>>> On Fri, 18 Jul 2008 16:57:50 +0200, Arno Lehmann said:
> 
> 18.07.2008 16:35, Dan Langille wrote:
> > On Jul 17, 2008, at 5:55 PM, Andrea Venturoli wrote:
> > 
> >> Frank Sweetser ha scritto:
> >>
> >>> I would suggest starting it up manually in a terminal with debug  
> >>> output
> >>> enabled.  The -f option will keep it in the foreground, and -d100  
> >>> will set the
> >>> debug level to 100 (a good start).  Using the script command will  
> >>> make it easy
> >>> to capture all of the output to a file as well.
> >>>
> >> I've done this.
> >> Apart from the obvious fact that it is crashing, I cannot make too  
> >> much
> >> sense of this data.
> >> Here it is for anyone interested: http://netfence.it/bacula.log
> > 
> > 
> > Signal 11... hmm.
> > 
> > Googling finds: http://www.bitwizard.nl/sig11/
> 
> Beware... that looks like really old information. Much of it is 
> useless today (but was correct when written...)

It's probably stil vaguely correct for the topic of the page: compiling the
Linux kernel.  GCC is generally quite reliable for C code, so it is very
unlikely that you will see a segmenation fault caused by software in that
case.

For bacula, it seems more likely to be software unfortunately...

__Martin

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users