> Tempting to skip all symbols with more than one digit (or maybe just more
> than one consecutive digit?), as guessing among per-chip symbols from, say,
> the ar* or dc* families is an exercise in futility.
Maybe. However, I couldn't come up with a criterion I was happy with.
Filtering three cons
*/
> if (strchr(sym, '.') != NULL || strchr(sym, '$') != NULL)
> continue;
> + /* guessing retguard symbols is no fun */
> + if (strncmp(sym, "__retguard", 10) == 0)
> + continue;
>
> break;
> }
>
>
x27;$') != NULL)
continue;
+ /* guessing retguard symbols is no fun */
+ if (strncmp(sym, "__retguard", 10) == 0)
+ continue;
break;
}
The diff below teaches the lldb assembly inspector to skip over the
retguard instrumentation when traversing function prologues.
ok?
diff --git
a/gnu/llvm/tools/lldb/source/Plugins/UnwindAssembly/x86/x86AssemblyInspectionEngine.cpp
b/gnu/llvm/tools/lldb/source/Plugins/UnwindAssembly/x86
That's great!
> Hi,
> The problems caused by enabling both kcov and retguard was due to the
> increased kernel size. Now that NKL2_KIMG_ENTRIES has been bumped on
> amd64, it's no longer a problem.
>
> Comments? OK?
>
> Ind
Hi,
The problems caused by enabling both kcov and retguard was due to the
increased kernel size. Now that NKL2_KIMG_ENTRIES has been bumped on
amd64, it's no longer a problem.
Comments? OK?
Index: arch/amd64/conf/Makefile.
Edd Barrett:
> > lang/pypy retguard
>
> I'm looking into PyPy.
>
> Can you provide the build output?
Oops, sorry, I forgot to save the logs before I cleaned the machines
yesterday. Should be straightforward to reproduce, though. At
some point the bui
On Mon, Aug 21, 2017 at 12:13:05PM -, Christian Weisgerber wrote:
> lang/pypy retguard
I'm looking into PyPy.
Can you provide the build output?
Cheers
--
Best Regards
Edd Barrett
http://www.theunixzoo.co.uk
es with a retguard snapshot:
lang/node retguard
lang/pypy retguard
And a bunch of ports using java, although jdk itself built fine:
databases/db/v4 retguard (java)
devel/intellij retguard (java)
editors/libreoffice
