| Summary: | tvtime crashed with SIGSEGV in __GI___strdup() | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | triniton <trinitonadam> | ||||||
| Component: | tvtime | Assignee: | Tomas Smetana <tsmetana> | ||||||
| Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||
| Severity: | unspecified | Docs Contact: | |||||||
| Priority: | unspecified | ||||||||
| Version: | rawhide | CC: | geoubuntu, tsmetana | ||||||
| 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: | 2014-04-16 07:38:13 UTC | Type: | Bug | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Attachments: |
|
||||||||
Created attachment 789405 [details]
StacktraceSource
Looks like a similar case to the bug #1000210: tvtime wants to read from user's home directory and expects the HOME environment variable to be set. An workaround for this bug and bug #1000210: In files src/tvtime-command.c src/tvtime-configure.c src/tvtime-scanner.c src/tvtime.c add this lines after int main( int argc, char **argv ): int main( int argc, char **argv ) { + if( !getenv( "HOME" ) ) { + fprintf( stderr, _("tvtime requires environment variable HOME to be set.\n") ); + exit( 1 ); + } + + if( strlen( getenv( "HOME" ) ) > 230 ) { + fprintf( stderr, _("The environment variable HOME is too long.\n") ); + exit( 1 ); + } + |
Created attachment 789404 [details] [1] Description of problem: tvtime crashes with exit status 139. The attachment [1] contains a testcase (under ./crash) crashing the program. It ensures that you can easily reproduce the bug. Additionally, under ./crash_info/, we include more information about the crash such as a core dump, the dmesg generated by the crash, and its output.