Review Request 123191: Show more of the backtrace of the found problems. Also show the auxiliary backtrace ( source of the problem )
Laszlo Kis-Adam
dfighter1985 at gmail.com
Wed Apr 1 01:01:24 UTC 2015
> On March 31, 2015, 8:03 a.m., Kevin Funk wrote:
> > We need to make it clear where those two backtraces come from, otherwise it might be confusing.
> >
> > Maybe show the "Invalid read at ...", and "Address 0x0 stack'd by ..." messages in the listing, too?
>
> Laszlo Kis-Adam wrote:
> OK, I'll do it.
Better this way?
http://www.picbutler.de/bild/321368/20150401000002316kh1at.jpg
- Laszlo
-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/123191/#review78264
-----------------------------------------------------------
On April 1, 2015, 2:59 a.m., Laszlo Kis-Adam wrote:
>
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> https://git.reviewboard.kde.org/r/123191/
> -----------------------------------------------------------
>
> (Updated April 1, 2015, 2:59 a.m.)
>
>
> Review request for KDevelop.
>
>
> Repository: kdev-valgrind
>
>
> Description
> -------
>
> Show more of the backtrace of the found problems. Also show the auxiliary backtrace ( source of the problem )
>
>
> Diffs
> -----
>
> marks.cpp 9adca2b
> models/memcheckitemsimpl.h b6d7a96
> models/memcheckitemsimpl.cpp 1b50b96
> models/memcheckmodel.cpp ad42605
>
> Diff: https://git.reviewboard.kde.org/r/123191/diff/
>
>
> Testing
> -------
>
> * built
> * installed
> * it works as intended.
>
> Take a look at the difference:
> Before:
> http://www.picbutler.de/bild/321320/20150331000002312k3ncw.jpg
>
> After:
> http://www.picbutler.de/bild/321321/201503310000023132yrhe.jpg
>
>
> Thanks,
>
> Laszlo Kis-Adam
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kdevelop-devel/attachments/20150401/61937295/attachment-0001.html>
More information about the KDevelop-devel
mailing list