michalbiesek

@thinkingfish I would like to leave the fix to you, since I will not be able to perform this fix in next two weeks.

@jschmieg I think I handled the situation to detect where allocation should go (PMEM or DRAM) in _sdsnewlen function to detect when call pmem related memory function later. I recommend...

While working on it, I can confirm that the test reintroduced in 24e17d5 will pass if we opt out from all the assembly part and just return -1 without calling...

The second thing besides above is after discussion with @jrcheli is when run `scope k8s` we should ensure that `scope daemon` should run in every node - this thing can...

## Current configuration options ### Default Variant By default backtrace logging is disabled Example command ``` scope ls ``` ### Full Backtrace Variant To enable full backtrace logging for memory...

The main idea is to inform the existing JVM - the one which we can attach to be aware of **Agent_OnAttach** interface. [DRAFT] Java process Byte code instrumentation on attach...

**Current status:** - To force Java Virtual Machine to call Agent_OnAttach interface - a native implementation of loadAgentPath was provided in scope - see details #617 - Need to investigate...

**Current status:** During working on this issue after checking different versions of Java I discover a crash when attaching on Java with SIGINT on the `Dockerfile.glibc,` this will be addressed...

Current status: #619 address the bug with the corner case of handling Shared Object library and GOT entry: ``` 7f4bc9a37000-7f4bc9a3a000 ---p 00000000 00:00 0 7f4bc9a3a000-7f4bc9b38000 rw-p 00000000 00:00 0 ```...

Regarding https://github.com/criblio/appscope/pull/617 - native implementation of loadAgentPath seems to works fine - the discovered limitation is that we need to modify logic of callback, with AgentOnLoad we will not miss...