Bug 688978

Summary: guestfish: double free or corruption if TMPDIR points to a non-existent directory
Product: [Community] Virtualization Tools Reporter: Richard W.M. Jones <rjones>
Component: libguestfsAssignee: Richard W.M. Jones <rjones>
Status: CLOSED INSUFFICIENT_DATA QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: unspecifiedCC: mbooth, mgoldman, virt-maint
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-04-12 17:11:53 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Richard W.M. Jones 2011-03-18 17:44:59 UTC
Description of problem:

[goldmann@work ~]$ TMPDIR=sadsadsa guestfish -a /dev/null 

Welcome to guestfish, the libguestfs filesystem interactive shell for
editing virtual machine filesystems.

Type: 'help' for help on commands
      'man' to read the manual
      'quit' to quit the shell

><fs> launch 
libguestfs: error: sadsadsa/libguestfsXXXXXX: cannot create temporary directory: No such file or directory
*** glibc detected *** guestfish: double free or corruption (out): 0x00007fffeaa11510 ***
======= Backtrace: =========
/lib64/libc.so.6[0x32dd476d63]
/usr/lib64/libguestfs.so.0[0x37464550a6]
guestfish[0x4234f8]
guestfish[0x4238aa]
guestfish[0x424707]
/lib64/libc.so.6(__libc_start_main+0xfd)[0x32dd41ee5d]
guestfish[0x40a3d9]
======= Memory map: ========

Version-Release number of selected component (if applicable):

guestfish 1.8.1

(NOTE: RWMJ tested this on 1.9.11 and could not reproduce
the problem.  However I'm filing this bug just in case the
problem is still there, just hidden).

How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Richard W.M. Jones 2011-03-18 18:50:56 UTC
This appears to have fixed itself magically between 1.8.1
and 1.8.2.  Since I'm not sure what commit fixed it, I'm
leaving this bug open out of caution.

Comment 2 Richard W.M. Jones 2011-04-12 17:11:53 UTC
This is not happening with 1.9.18.  Also I checked with
valgrind, and it cannot find anything.