doxygen assert failure: *** buffer overflow detected ***: doxygen terminated

Bug #493350 reported by Christopher Backhouse
26
This bug affects 2 people
Affects Status Importance Assigned to Milestone
doxygen (Ubuntu)
Invalid
Medium
Unassigned
Nominated for Lucid by reini

Bug Description

Binary package hint: doxygen

Reproducible. Running doxygen on own code.

ProblemType: Crash
Architecture: i386
AssertionMessage: *** buffer overflow detected ***: doxygen terminated
CheckboxSubmission: a681fcf6b9e1fe3688b4f273cfa1bb89
CheckboxSystem: d00f84de8a555815fa1c4660280da308
CrashCounter: 1
Date: Sun Dec 6 22:47:22 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/doxygen
Package: doxygen 1.6.1-1
ProcCmdline: doxygen Doxyfile
ProcEnviron:
 LANGUAGE=en_GB.UTF-8
 PATH=(custom, user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-16.52-generic-pae
Signal: 6
SourcePackage: doxygen
StacktraceTop:
 __kernel_vsyscall ()
 *__GI_raise (sig=6)
 *__GI_abort () at abort.c:92
 __libc_message (do_abort=2,
 *__GI___fortify_fail (
Title: doxygen assert failure: *** buffer overflow detected ***: doxygen terminated
Uname: Linux 2.6.31-16-generic-pae i686
UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin netdev plugdev powerdev sambashare scanner video
XsessionErrors:
 (gnome-settings-daemon:2461): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
 (polkit-gnome-authentication-agent-1:2582): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
 (nautilus:2584): Eel-CRITICAL **: eel_preferences_get_boolean: assertion `preferences_is_initialized ()' failed
 (gnome-panel:2565): Gdk-WARNING **: /build/buildd/gtk+2.0-2.18.3/gdk/x11/gdkdrawable-x11.c:952 drawable is not a pixmap or window
 (gnome-power-manager:2580): Gdk-CRITICAL **: gdk_window_thaw_toplevel_updates_libgtk_only: assertion `private->update_and_descendants_freeze_count > 0' failed

Revision history for this message
Christopher Backhouse (cjbackhouse) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt (retraced)

StacktraceTop:__kernel_vsyscall ()
*__GI_raise (sig=6)
*__GI_abort () at abort.c:92
__libc_message (do_abort=2,
*__GI___fortify_fail (

Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt (retraced)
Changed in doxygen (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
Revision history for this message
Matthias Klose (doko) wrote :

please could you provide the files to reproduce the crash?

visibility: private → public
Changed in doxygen (Ubuntu):
status: New → Incomplete
Revision history for this message
Christopher Backhouse (cjbackhouse) wrote :

On further investigation, this has something to do with my .hg directory rather than anything to do with the code being documented.

I can reproduce the crash with

cd doxgen_crasher
doxygen Doxyfile

I haven't gone through the .hg directory to find which file exactly triggers it.

Revision history for this message
Christopher Backhouse (cjbackhouse) wrote :

> I haven't gone through the .hg directory to find which file exactly triggers it.

I tell a lie. The crash is triggered by the file "plaibuildlib.d" which is some binary junk, but is matched by FILE_PATTERNS in my (autogenerated) Doxyfile. The attachment contains a simplified testcase with just this file.

So, it's basically my problem for trying to document a non-source file, but I assume that even so doxygen shouldn't outright crash.

Revision history for this message
reini (rrumberger) wrote :

I have only source files I'm trying to document and am getting the same crash (see bug #579951) in Lucid.

Revision history for this message
reini (rrumberger) wrote :

Marking as new to get some attention and also since the requested files have been provided.

Changed in doxygen (Ubuntu):
status: Incomplete → New
Revision history for this message
dino99 (9d9) wrote :

This version is outdated and no more supported

Changed in doxygen (Ubuntu):
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.