Are you sure this is not just an artifact of stdio buffering? I tried the
same experiment, but I placed a real log statement, and I could see that
all the LoadModuleAtAddress calls happen between the $T and $c packets in
the gdb-remote packet sequence.
The module loading should be synchronous, so
> On Apr 11, 2017, at 5:33 AM, Pavel Labath wrote:
>
> Are you sure this is not just an artifact of stdio buffering? I tried the
> same experiment, but I placed a real log statement, and I could see that all
> the LoadModuleAtAddress calls happen between the $T and $c packets in the
> gdb-rem
See https://bugs.llvm.org/show_bug.cgi?id=25806 for details about why we
can't set breakpoint in the static initializer (it is an LLDB bug).
For your investigation a few pointers/guesses (assuming it is not some
stdout displaying issue what I consider unlikely based on your description):
* Do your
On 11 April 2017 at 15:56, Greg Clayton wrote:
>
> On Apr 11, 2017, at 5:33 AM, Pavel Labath wrote:
>
> Are you sure this is not just an artifact of stdio buffering? I tried the
> same experiment, but I placed a real log statement, and I could see that
> all the LoadModuleAtAddress calls happen
