Re: RFR: 8280601: ClhsdbThreadContext.java test is triggering codecache related assert in PointerFinder.find() [v2]

2022-02-01 Thread Chris Plummer
On Fri, 28 Jan 2022 04:07:40 GMT, Chris Plummer wrote: >> It's possible for an address to be in the codecache but not in any CodeBlob. >> Don't assert in this case. >> >> Also I ran into a couple of other asserts listed below. It looks like since >> dumping the threadcontext can result in

Re: RFR: 8280601: ClhsdbThreadContext.java test is triggering codecache related assert in PointerFinder.find() [v2]

2022-02-01 Thread Serguei Spitsyn
On Fri, 28 Jan 2022 04:07:40 GMT, Chris Plummer wrote: >> It's possible for an address to be in the codecache but not in any CodeBlob. >> Don't assert in this case. >> >> Also I ran into a couple of other asserts listed below. It looks like since >> dumping the threadcontext can result in

Re: RFR: 8280601: ClhsdbThreadContext.java test is triggering codecache related assert in PointerFinder.find() [v2]

2022-02-01 Thread Chris Plummer
On Wed, 26 Jan 2022 22:50:47 GMT, Serguei Spitsyn wrote: >> Chris Plummer has updated the pull request incrementally with one additional >> commit since the last revision: >> >> Guard against invalid CodeBlobs that may throw exceptions. > > Looks okay to me. > Thanks, > Serguei @sspitsyn

Re: RFR: 8280601: ClhsdbThreadContext.java test is triggering codecache related assert in PointerFinder.find() [v2]

2022-01-28 Thread Kevin Walls
On Fri, 28 Jan 2022 04:07:40 GMT, Chris Plummer wrote: >> It's possible for an address to be in the codecache but not in any CodeBlob. >> Don't assert in this case. >> >> Also I ran into a couple of other asserts listed below. It looks like since >> dumping the threadcontext can result in

Re: RFR: 8280601: ClhsdbThreadContext.java test is triggering codecache related assert in PointerFinder.find()

2022-01-27 Thread Chris Plummer
On Tue, 25 Jan 2022 22:07:37 GMT, Chris Plummer wrote: > It's possible for an address to be in the codecache but not in any CodeBlob. > Don't assert in this case. > > Also I ran into a couple of other asserts listed below. It looks like since > dumping the threadcontext can result in using

Re: RFR: 8280601: ClhsdbThreadContext.java test is triggering codecache related assert in PointerFinder.find() [v2]

2022-01-27 Thread Chris Plummer
On Wed, 26 Jan 2022 14:27:54 GMT, Kevin Walls wrote: >> Chris Plummer has updated the pull request incrementally with one additional >> commit since the last revision: >> >> Guard against invalid CodeBlobs that may throw exceptions. > >

Re: RFR: 8280601: ClhsdbThreadContext.java test is triggering codecache related assert in PointerFinder.find() [v2]

2022-01-27 Thread Chris Plummer
> It's possible for an address to be in the codecache but not in any CodeBlob. > Don't assert in this case. > > Also I ran into a couple of other asserts listed below. It looks like since > dumping the threadcontext can result in using PointerFinder with fairly > random addresses, it is doing

Re: RFR: 8280601: ClhsdbThreadContext.java test is triggering codecache related assert in PointerFinder.find()

2022-01-26 Thread Serguei Spitsyn
On Tue, 25 Jan 2022 22:07:37 GMT, Chris Plummer wrote: > It's possible for an address to be in the codecache but not in any CodeBlob. > Don't assert in this case. > > Note I couldn't reproduce this failure. Not sure why since it seemed to > reproduce pretty readily in our CI tier7, and I ran

Re: RFR: 8280601: ClhsdbThreadContext.java test is triggering codecache related assert in PointerFinder.find()

2022-01-26 Thread Kevin Walls
On Tue, 25 Jan 2022 22:07:37 GMT, Chris Plummer wrote: > It's possible for an address to be in the codecache but not in any CodeBlob. > Don't assert in this case. > > Note I couldn't reproduce this failure. Not sure why since it seemed to > reproduce pretty readily in our CI tier7, and I ran

RFR: 8280601: ClhsdbThreadContext.java test is triggering codecache related assert in PointerFinder.find()

2022-01-25 Thread Chris Plummer
It's possible for an address to be in the codecache but not in any CodeBlob. Don't assert in this case. Note I couldn't reproduce this failure. Not sure why since it seemed to reproduce pretty readily in our CI tier7, and I ran with the same options. - Commit messages: - Don't