Review Request: Fix pretty printer for QString.

[Niko Sams]

> On Oct. 5, 2011, 7:09 a.m., Niko Sams wrote:
> > Seems ok. Though this would be probably needed for every printer? (better: gdb should handle exceptions gracefully)
> > 
> > Would be great if you could add a unit test for an uninitialized string.

see also this bug: http://sourceware.org/bugzilla/show_bug.cgi?id=11407
it addresses this issue, and seems to be fixed for 7.3. I haven't tried it yet though.

which gdb version did you test with?


- Niko


-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/102778/#review7098
-----------------------------------------------------------


On Oct. 4, 2011, 11:07 p.m., Maciek Zarzycki wrote:
> 
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> http://git.reviewboard.kde.org/r/102778/
> -----------------------------------------------------------
> 
> (Updated Oct. 4, 2011, 11:07 p.m.)
> 
> 
> Review request for KDevelop.
> 
> 
> Description
> -------
> 
> The printer may be ran when the QString object is not yet initialized.
> In this case we might get memory access violation resulting from undefined value of QString::size.
> Wrap the printer inside try/except to prevent this.
> 
> 
> This addresses bug 280201.
>     http://bugs.kde.org/show_bug.cgi?id=280201
> 
> 
> Diffs
> -----
> 
>   debuggers/gdb/printers/qt4.py 51f3a11 
> 
> Diff: http://git.reviewboard.kde.org/r/102778/diff/diff
> 
> 
> Testing
> -------
> 
> Ran unit tests.
> 
> 
> Thanks,
> 
> Maciek Zarzycki
> 
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kdevelop-devel/attachments/20111005/fb39ce0b/attachment.html>