Re: crash when entering some .tar files

[wwp <subscript free fr>]

Hello Andrew,


On Tue, 2 Mar 2004 16:48:37 +0200 (EET) "Andrew V. Samoilov" <andrew email zp ua> wrote:

> > I'm happily using mc for ages (currently 4.6.1-pre1 compiled from sources,
> > linux 2.4.24 x86, glibc 2.2.5), and encountering now a crash when entering
> > some kind of .tar files. The error follows:
> > 
> > (process:12769): GLib-CRITICAL **: file gstrfuncs.c: line 232 (g_strconcat): assertion `string1 != NULL' failed
> > 
> > 
> > I was not able to access to the mailing list archives yet, is this a known
> > issue or should I submit a URL to such .tar file (mostly contains files only,
> > for instance /lib content)?
> > BTW, GNU tar --version says: 1.13.25.
> 
> Submit URL to such .tar please or we would appreciate a stack trace. 

Yep, you will find the crashing .tar.bz2 (.tar would be enough, but I crunched
it for bandwidth purposes) here:
	http://nanabozo.free.fr/tmp/mc/test.tar.bz2


Ran under gdb, backtrace follows:

Program received signal SIGSEGV, Segmentation fault.
0x0809804c in canonicalize_pathname ()
(gdb) bt
#0  0x0809804c in canonicalize_pathname ()
#1  0x080c9332 in vfs_s_find_entry_tree ()
#2  0x080cad5d in vfs_s_resolve_symlink ()
#3  0x080c95d2 in vfs_s_find_entry_tree ()
#4  0x080c82d2 in vfs_s_find_inode ()
#5  0x080c9e22 in vfs_s_stat ()
#6  0x080ce0da in mc_stat ()
#7  0x080698da in handle_dirent ()
#8  0x080684ee in do_load_dir ()
#9  0x0807e056 in _do_panel_cd ()
#10 0x0807d71d in do_cd ()
#11 0x0806adf2 in exec_extension ()
#12 0x0806a544 in regex_command ()
#13 0x0808d441 in do_enter_on_file_entry ()
#14 0x0808b394 in panel_key ()
#15 0x08087f5a in panel_callback ()
#16 0x08067cab in dlg_key_event ()
#17 0x08067757 in dlg_process_event ()
#18 0x08067dc7 in frontend_run_dlg ()
#19 0x08067838 in run_dlg ()
#20 0x0807f0bc in setup_panels_and_run_mc ()
#21 0x0807cccd in main ()
(gdb) 


Full backtrace:
is there a way I can get symbols once mc is installed thru `make install`?
The bin seems not to be stripped but I could not get symbol info.
Anyway there must be smth broken when parsing such .tar archive thru
vfs, maybe in related to symlink inside. You will probably be able to
see that by yourself!


BTW I'm still using 4.6.1-pre1 (plus versionsort patch).


Regards,

-- 
wwp