Bug 14872

Summary:	rarian-sk-get-cl assumes USERNAME environment variable set, crashes if not
Product:	Rarian	Reporter:	paul <ephraim_owns>
Component:	General	Assignee:	Don Scorgie <Don>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	medium
Version:	unspecified
Hardware:	PowerPC
OS:	Mac OS X (All)
Whiteboard:
i915 platform:		i915 features:

Description paul 2008-03-06 15:49:29 UTC

# gdb /opt/local/bin/rarian-sk-get-cl 
GNU gdb 5.3-20030128 (Apple version gdb-282) (Fri Jun 13 03:33:07 GMT 2003)
Copyright 2003 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "powerpc-apple-darwin".
Reading symbols for shared libraries ... done
(gdb) r C scrollkeeper_cl.xml
Starting program: /opt/local/bin/rarian-sk-get-cl C scrollkeeper_cl.xml
Reading symbols for shared libraries +. done

Program received signal EXC_BAD_ACCESS, Could not access memory.
0x90000e60 in strlen ()
(gdb) bt
#0  0x90000e60 in strlen ()
#1  0x000033b8 in find_dump_name() () at /Source/rarian/rarian/util/rarian-sk-get-cl.cpp:169
#2  0x00003668 in main (argc=3, argv=0xbffff9d4) at /Source/rarian/rarian/util/rarian-sk-get-cl.cpp:225
(gdb) set env USERNAME root
(gdb) r C scrollkeeper_cl.xml
The program being debugged has been started already.
Start it from the beginning? (y or n) y
Starting program: /opt/local/bin/rarian-sk-get-cl C scrollkeeper_cl.xml
/tmp/scrollkeeper-root/contents.1

Program exited normally.
(gdb) 

on my system, only USER gets defined

Comment 1 Don Scorgie 2008-07-29 11:32:04 UTC

Thanks for the bug report.  Fixed in SVN and will appear in 0.8.1

2008-07-29  Don Scorgie  <Don@Scorgie.org>

	* util/rarian-sk-get-cl.cpp: 
	If $USERNAME isn't set, use default (UNKNOWN)
	bug #14872

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.