On Sat, 2007-12-08 at 15:15 -0500, Albert Cahalan wrote:
> On Dec 8, 2007 4:40 AM, Caroline Ford <caroline.ford.work@...> wrote:
> > I've submitted one bug to our bug tracker - a crash bug with backtraces.
> It's not terribly helpful. It shows the obvious
> signature of heap corruption, a crash in _int_malloc.
> The bad code could be anywhere; your stack trace
> does not point to the bad code. It is misleading.
> To catch an overflow when it happens, right as
> it is corrupting the heap data structures, you need
> either valgrind or electric fence. Valgrind works all
> by itself. Electric fence needs to be used with gdb.
Well this is the info Ubuntu collects from its crash logs and the back
traces it generates.
I don't know what to suggest - this is the information they are giving
us. Their debugging procedures and bug triaging procedures use gdb,
their automatic crash dump process (apport) does the same I think.
It's not *my* bug so I can't get any more info..