On Fri, 2017-02-10 at 17:50 +0100, Ulf Hermann wrote:
> > Try sending suspicious content via something like fpaste.org.
>
> I don't think it's very suspicious, but I don't intend to start a pointless
> argument as first thing I do here ;)
>
> fpaste.org won't accept it either, but paste.kde.or
On Fri, 2017-02-10 at 15:19 +0100, Ulf Hermann wrote:
> This is useful to test unwinding without debug information. The
> binaries being examined might still have frame pointers that allow
> us to bridge the unknown symbols.
>
> Signed-off-by: Ulf Hermann
Applied even though the new option is no
On Fri, 2017-02-10 at 15:19 +0100, Ulf Hermann wrote:
> When unwinding by frame pointer the unwinder might ask for invalid
> addresses. We don't have to fail the test in this case. In fact
> any broken dwarf information can lead to requests for invalid
> addresses, also without frame pointer unwind
On Fri, 2017-02-10 at 15:18 +0100, Ulf Hermann wrote:
> Some test binaries were missing and showed up in "git status".
>
> Signed-off-by: Ulf Hermann
Thanks, applied. (Although, this is why I don't like srcdir == builddir
builds, but it is supported).
But note that your patch seemed to have bee
Make sure that if we have really many labels the tempsym doesn't get
truncated because it is too small to hold the whole name.
This doesn't enable -Wformat-truncation=2 or fix other "issues" pointed
out by enabling this warning because there are currently some issues
with it. https://gcc.gnu.org/b
