🚀 go-pugleaf

There seems to be a bug in GNU tar 1.11's "-v" option.  I am running
on an Intel SVR4 (Esix 4.0.3A) machine, compiling with gcc v2.1.
Aside from commenting out a few

extern char *valloc();

declarations (because they conflicted with the ones in <stdlib.h>), I
have not modified the source.

The problem is that tar prints out a blank line where the filename
should be when -v is given during archive creation (i.e., with the
-c flag).  Using multiple -v's, which should increase the debugging
level, results in a segmentation fault.

I have traced through the code, and it seems that the problem is that
the global current_file_name is not being set correctly when
print_header is called.  print_header attempts to get the current file
name from current_file_name, and so it prints out nothing.  tar
segvios when multiple -v's are given because at the higher debugging
levels, tar tries to do strlen(current_file_name), which results in
strlen being passed a null pointer.

Where and how should current_file_name be set?

-- 
Marc Unangst                | Real men don't use Windows.  Real men use X. 
mju@mudos.ann-arbor.mi.us   | Only a real man would use a GUI where the
                            | shift keys after "Alt" are "Super" and "Hyper."