[Posted and mailed]

In article <199803281223.NAA01913@lyssa.owl.de>,
	Matthias Scheler <tron@lyssa.owl.de> writes:

>>Description:
> When I tried to do the weekly backup today the "dump" of my root partition
> stopped after a short time with "SIGSEGV: ABORTING!" message. After I copied
> "/sbin/dump" from an 1.3 system everything worked fine again.
> 

I did a bit of investigation on that after trying to backup my system. The
problem lies in the option "-u" (update dumpdates) when /etc/dumpdates
exists:

magick@bundy:~/bin#rm /etc/dumpdates                                      
magick@bundy:~/bin#dump -0 -B 2500000 -b 10 -u -f /dev/null /             
  DUMP: WARNING: no file `/etc/dumpdates', making an empty one            
...                                                                       
  DUMP: Average transfer rate: 737 KB/s                                   
  DUMP: level 0 dump on Thu Jan  1 01:00:00 1970                          
  DUMP: Closing /dev/null                                                 
  DUMP: DUMP IS DONE                                                      
                           
[now /etc/dumpdates exists]
                                            
magick@bundy:~/bin#dump -0 -B 2500000 -b 10 -u -f /dev/null /          
...                                                                    
  DUMP: Average transfer rate: 737 KB/s                                
  DUMP: SIGSEGV: ABORTING!                                    
  DUMP: SIGSEGV: ABORTING!                                          
  DUMP: SIGSEGV: ABORTING!    
  DUMP: SIGSEGV: ABORTING!                                             
Segmentation fault                                                     

As you can see, the same call once works and once breaks depending on the
existance of /etc/dumpdates. 

Hope the helps a bit in finding the error.

-- 
Mario Kemper
magick@bundy.lip.owl.de