Re: [blink-dev] Debugging compressed pointers in Blink

2022-10-12 Thread Anton Bikineev
tian > > On Tue, Oct 11, 2022 at 11:00 AM Dave Tapuska > wrote: > >> Anton, can you add this to >> https://source.chromium.org/chromium/chromium/src/+/main:docs/linux/debugging.md >> ? >> >> On Tue, Oct 11, 2022 at 10:19 AM Anton Bikineev >> wrote: >

Re: [blink-dev] Debugging compressed pointers in Blink

2022-10-11 Thread Anton Bikineev
improved in the future. On Tue, Oct 11, 2022 at 4:05 PM Anton Bikineev wrote: > Which should hopefully be callable from the debugger and not eliminated by >> the linker? > > We can apply __attribute__((used,retain)) to make sure that the linker > doesn't strip the functio

Re: [blink-dev] Debugging compressed pointers in Blink

2022-10-11 Thread Anton Bikineev
I found that I can avoid the issue with this in args.gn: >> >> cppgc_enable_caged_heap = false >> cppgc_enable_pointer_compression = false >> >> ... but I would prefer a better solution. >> >> On Mon, Oct 10, 2022 at 10:22 AM Ian Kilpatrick >&

Re: [blink-dev] Debugging compressed pointers in Blink

2022-09-22 Thread Anton Bikineev
alue? > > Daniel > > On Thu, 22 Sept 2022 at 08:43, Anton Bikineev > wrote: > >> We have plans to provide more debugging tooling for Oilpan. I haven't had >> a need to examine compressed pointers myself, however I see that some >> simple gdb/windbg function tha

Re: [blink-dev] Debugging compressed pointers in Blink

2022-09-22 Thread Anton Bikineev
We have plans to provide more debugging tooling for Oilpan. I haven't had a need to examine compressed pointers myself, however I see that some simple gdb/windbg function that'd follow pointers would be useful. On Thu, Sep 22, 2022 at 1:14 AM Kentaro Hara wrote: > +Michael Lippautz > > 2022年9月2