Hello
This bug is marked as "serious" which is "release critical" but shows no
progress since some months.
Is the bug is still present in the latest upstream version? If so you
could contact the author for help, else consider to either downgrade the
bug (no good idea, I guess), remove the package
I looked at this bug and ran doc++ under valgrind on i386, and it found
a problem:
==24836== Mismatched free() / delete / delete []
==24836==at 0x1B904B04: free (vg_replace_malloc.c:152)
==24836==by 0x80813A6: TOClist::~TOClist()
(in /home/liw/Debian-bug-fixing/doc++/doc++-3.4.10/src/doc++
Processing commands for [EMAIL PROTECTED]:
> severity 292337 serious
Bug#292337: doc++ segfaults on m68k, including during its own build
Severity set to `serious'.
> thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system ad
severity 292337 important
thanks
El miÃ, 26-01-2005 a las 06:24 -0700, Adam Conrad escribiÃ:
> Package: doc++
> Version: 3.4.10-3
> Severity: serious
>
> Building dmachinemon on m68k fails[1] due to a segfault in doc++. Upon
> further investigation (attempting a rebuild of doc++ to see if that
>
Processing commands for [EMAIL PROTECTED]:
> severity 292337 important
Bug#292337: doc++ segfaults on m68k, including during its own build
Severity set to `important'.
> thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system ad
Package: doc++
Version: 3.4.10-3
Severity: serious
Building dmachinemon on m68k fails[1] due to a segfault in doc++. Upon
further investigation (attempting a rebuild of doc++ to see if that
would magically make it happy), it appears that doc++ segfaults when
creating its own docs during its build
6 matches
Mail list logo