Comment 3 for bug 971174

The workaround destroys the output of dmalloc, so I see things like
Error: %s (err %d)
and
%ld: %lu: Warning tried to free (0) from '%s'
%ld: %lu: error details: %s
%ld: %lu: pointer '%#lx' from '%s' prev access '%s'

none of which is particularly usefull, and I might as well not be using dmalloc at this point.

Here's the relevant stack trace info...

#0 _IO_vfprintf_internal
#1 _IO_vfprintf
#2 loc_vsnprintf
#3 loc_snprintf
#4 _dmalloc_vmessage
#5 dmalloc_message
#6 dmalloc_error
#7 dmalloc_in
#8 dmalloc_free
#9 free ()
.
. (pattern above repeats....a lot....)
.
#29222 free
#29223 _IO_vfprintf_internal
#29224 _IO_vfprintf
#29225 loc_vsnprintf
#29226 loc_snprintf
#29227 dmalloc_chunk_desc_pnt
#29228 dmalloc_chunk_free
#29229 dmalloc_free
#29230 free
#29231 _IO_vfprintf_internal
#29232 buffered_vfprintf
#29233 _IO_vfprintf_internal
#29234 ___vfprintf_chk
#29235 xmlGenericErrorDefaultFunc

was this perhaps fixed in a newer ubuntu release since I see the last comment was June 2012?