found 676006 0.5.0~svn5126+dfsg.1-1 severity 676006 normal thanks
On 06/18/2012 10:53 PM, Gilles Filippini wrote: > > The issue reported by g++ "taking address of temporary array" *is* > fixed. In this context (AIUI), "temporary" means that there is no > certainty that the address is still valid at the time > callback_list_call_attr_1() is called. its not fixed, its just silenced. It still takes the address of a temporary and passes it out of the stack frame. Only the ftbs is fixed so it is not serious anymore. I have decreased the severity to normal as it may not cause any noticeable issues. > > It's another kind of uncertainty you'll find waaaay more time in the > navit source code. The question is then : will the array address be > still in use after the exit from RenderArea::keyPressEvent() method? > very likely, its passed into a callback so unless the callback runs in a thread which preempts the current frame it will be popped of the stack before the use. gui callbacks seldom run in their own threads and the function returns immediately, so chances that this happens are pretty much 100%. > > A correct fix implies knowing precisely how the triggered callbacks are > supposed to use the address. I don't, and will appreciate any findings > you could share. > > Anyway, #676006 is closed and new bugs should have their own bugreports. > its the same issue, so it can stay the same bug. As the maintainer you forward it to upstream so they can take care of it in the proper way.
signature.asc
Description: OpenPGP digital signature
