[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #53604] ASAN new-delete-type-mismatch error af

From: Rik
Subject: [Octave-bug-tracker] [bug #53604] ASAN new-delete-type-mismatch error after "close all"
Date: Fri, 13 Apr 2018 11:46:56 -0400 (EDT)
User-agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:55.0) Gecko/20100101 Firefox/55.0

Update of bug #53604 (project octave):

                  Status:                    None => Invalid                
             Open/Closed:                    Open => Closed                 


Follow-up Comment #10:

I think we can close this bug as an upstream issue with Qt that has since been

The long list of leaks is exactly what ASAN produces.  Almost all of them are
tagged as "Indirect leaks" which means they may not be true leaks, and digging
through each one to determine that would take eons.  The ones to really watch
are the direct leaks, for which we have about 56B.

I'm intrigued about the possible heap-buffer-overflow.  Can you open a new bug
report about that?  I suspect it is a bug in the driver nouveau_dri, but there
is the possibility that somehow the offset that Octave is supplying is
something crazy.

We could put an assert statement in the code temporarily to make sure that
offset is in some reasonable range ([-5, +5]).


Reply to this item at:


  Message sent via/by Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]