RFR: 8337299: vmTestbase/nsk/jdb/stop_at/stop_at002/stop_at002.java failure goes undetected

[Serguei Spitsyn]

On Thu, 1 Aug 2024 16:59:16 GMT, Chris Plummer <cjplummer at openjdk.org> wrote:

>> test/hotspot/jtreg/vmTestbase/nsk/jdb/stop_at/stop_at002/stop_at002.java line 147:
>> 
>>> 145:         }
>>> 146: 
>>> 147:         found = grep.findFirst("Breakpoint hit: \"thread=main\", ");
>> 
>> Q: Is it possible to check for the exact breakpoint location here?
>
> The problem is in the test we have:
> 
> `    static final String DEBUGGEE_LOCATION2 = DEBUGGEE_CLASS + "$Inner$MoreInner:78";`
> 
> And the jdb output is:
> 
> `reply[2]: Breakpoint hit: "thread=main", nsk.jdb.stop_at.stop_at002.stop_at002a$Inner$MoreInner.foo(), line=78 bci=0`
> 
> So I can't just search for DEBUGGEE_LOCATION2 in the output. I could do further factoring of DEBUGGEE_LOCATION2 so it is easier to construct a search pattern that would work, but I don't feel it is worth it.

Okay, thanks.

-------------

PR Review Comment: https://git.openjdk.org/jdk/pull/20366#discussion_r1702356366