lexgrog crashed with SIGSEGV in __GI__IO_default_xsputn()

[Benjamin Drung]

The program crashed.

ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: man-db 2.6.3-3
ProcVersionSignature: Ubuntu 3.8.0-13.22-generic 3.8.3
Uname: Linux 3.8.0-13-generic x86_64
ApportVersion: 2.9.2-0ubuntu1
Architecture: amd64
Date: Wed Mar 20 19:35:39 2013
ExecutablePath: /usr/bin/lexgrog
MarkForUpload: True
ProcCmdline: lexgrog /tmp/temp-lintian-lab-W_tFg3s4aG/pool/x/xdg-utils/xdg-utils_1.1.0~rc1-2ubuntu7_all_binary/unpacked/usr/share/man/man1/xdg-desktop-menu.1.gz
ProcEnviron: PATH=(custom, no user)
SegvAnalysis:
 Segfault happened at: 0x7fbc2b36c48b: rep movsq %ds:(%rsi),%es:(%rdi)
 PC (0x7fbc2b36c48b) ok
 source "%ds:(%rsi)" (0x7fffd11a6000) not located in a known VMA region (needed readable region)!
 destination "%es:(%rdi)" (0x7fbc2bce19d0) ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: man-db
StacktraceTop:
 ?? () from /lib/x86_64-linux-gnu/libc.so.6
 _IO_default_xsputn () from /lib/x86_64-linux-gnu/libc.so.6
 _IO_file_xsputn () from /lib/x86_64-linux-gnu/libc.so.6
 fwrite () from /lib/x86_64-linux-gnu/libc.so.6
 ?? () from /usr/lib/man-db/libman-2.6.3.so
Title: lexgrog crashed with SIGSEGV in _IO_default_xsputn()
UpgradeStatus: Upgraded to raring on 2013-02-25 (23 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

[Apport retracing service (apport)]

StacktraceTop:
 __GI__IO_default_xsputn (f=f@entry=0x7fbc2b6a1280 <_IO_2_1_stdout_>, data=data@entry=0x7fffd11a5630, n=n@entry=4097) at genops.c:464
 _IO_new_file_xsputn (n=4096, data=<optimized out>, f=0x7fbc2b6a1280 <_IO_2_1_stdout_>) at fileops.c:1364
 _IO_new_file_xsputn (f=0x7fbc2b6a1280 <_IO_2_1_stdout_>, data=<optimized out>, n=4096) at fileops.c:1286
 __GI__IO_fwrite (buf=buf@entry=0x7fffd11a4630, size=size@entry=1, count=count@entry=4096, fp=0x7fbc2b6a1280 <_IO_2_1_stdout_>) at iofwrite.c:43
 rpl_fwrite (stream=<optimized out>, n=4096, s=1, ptr=0x7fffd11a4630) at ../gnulib/lib/stdio.h:898

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.