rdesktop assert failure: *** glibc detected *** rdesktop: double free or corruption (fasttop): 0x089e99a0 ***
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| rdesktop (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
Bug Description
rdesktop crashes just after connecting to one of the servers
ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: rdesktop 1.7.0-1ubuntu2
ProcVersionSign
Uname: Linux 3.0.0-15-generic i686
ApportVersion: 1.23-0ubuntu4
Architecture: i386
AssertionMessage: *** glibc detected *** rdesktop: double free or corruption (fasttop): 0x089e99a0 ***
Date: Thu Dec 22 09:40:05 2011
ExecutablePath: /usr/bin/rdesktop
ProcCmdline: rdesktop -g 1920x1200 -k pl -u ottensten\
ProcEnviron:
LANGUAGE=
PATH=(custom, user)
LANG=pl_PL.UTF-8
SHELL=/bin/bash
Signal: 6
SourcePackage: rdesktop
StacktraceTop:
__libc_message (do_abort=2, fmt=0x474080 "*** glibc detected *** %s: %s: 0x%s ***\n") at ../sysdeps/
malloc_printerr (action=<optimized out>, str=<optimized out>, ptr=0x89e99a0) at malloc.c:6283
_int_free (av=0x4b0400, p=0x89e9998) at malloc.c:4795
__GI___libc_free (mem=0x89e99a0) at malloc.c:3738
XFree (data=0x89e99a0) at ../../src/
Title: rdesktop assert failure: *** glibc detected *** rdesktop: double free or corruption (fasttop): 0x089e99a0 ***
UpgradeStatus: Upgraded to oneiric on 2011-10-18 (64 days ago)
UserGroups: adm admin audio cdrom dialout dip floppy fuse libvirtd lpadmin plugdev sambashare scanner video
| karaluh (karaluh) wrote | #1 |
| Apport retracing service (apport) wrote This bug is a duplicate | #2 |
| visibility: | private → public |
| visibility: | private → public |
| tags: | removed: need-i386-retrace |
Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #649775, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.