gcal crashed with SIGSEGV in stpcpy()

[Keyur Gabani]

Binary package hint: gcal

1. install gcal from gutsy
2. run gcal

ProblemType: Crash
Architecture: amd64
CrashCounter: 1
Date: Sat Sep 29 19:28:00 2007
Dependencies:
 libgcc1 1:4.2.1-5ubuntu4
 gcc-4.2-base 4.2.1-5ubuntu4
 libncurses5 5.6+20070716-1ubuntu1
 libc6 2.6.1-1ubuntu8
DistroRelease: Ubuntu 7.10
ExecutablePath: /usr/bin/gcal
NonfreeKernelModules: cdrom
Package: gcal 3.01.1-5.1
PackageArchitecture: amd64
ProcCmdline: gcal
ProcCwd: /home/keyur
ProcEnviron:
 SHELL=/bin/bash
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_US.UTF-8
Signal: 11
SourcePackage: gcal
StacktraceTop:
 stpcpy () from /lib/libc.so.6
 ?? ()
 ?? ()
 __libc_start_main () from /lib/libc.so.6
 ?? ()
Title: gcal crashed with SIGSEGV in stpcpy()
Uname: Linux LIFE 2.6.22-12-generic #1 SMP Sun Sep 23 20:03:18 GMT 2007 x86_64 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev scanner video

[Apport retracing service (apport)]

StacktraceTop:stpcpy () from /lib/libc.so.6
?? ()
?? ()
__libc_start_main () from /lib/libc.so.6
?? ()

[Pedro Villavicencio (pedro)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please try to obtain a backtrace following the instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload the backtrace (as an attachment) to the bug report. This will greatly help us in tracking down your problem

[Keyur Gabani (halojetter)]

Here are Backtrace, Strace and Valgrind log file. Please let me know is more info is required

[Chris Coulson (chrisccoulson)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Can you try with latest Ubuntu release? Thanks in advance.

[Jonathan Thomas (echidnaman)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!