{"author_name":"eller","blog_title":"Kengo's blog","published":"2015-07-19 21:59:01","title":"How to track state of operand stack by FindBugs 3.0.1","provider_url":"https://hatena.blog","html":"<iframe src=\"https://hatenablog-parts.com/embed?url=https%3A%2F%2Fblog.kengo-toda.jp%2Fentry%2F2015%2F07%2F19%2F215901\" title=\"How to track state of operand stack by FindBugs 3.0.1 - Kengo&#39;s blog\" class=\"embed-card embed-blogcard\" scrolling=\"no\" frameborder=\"0\" style=\"display: block; width: 100%; height: 190px; max-width: 500px; margin: 10px 0px;\"></iframe>","provider_name":"Hatena Blog","categories":["FindBugs","\u30d7\u30ed\u30b0\u30e9\u30df\u30f3\u30b0","SLF4J","original"],"url":"https://blog.kengo-toda.jp/entry/2015/07/19/215901","author_url":"https://blog.hatena.ne.jp/eller/","description":"Yesterday I released findbugs-slf4j v1.2.0, which supports more useful analysis based on OpcodeStackDetector. Here I will summarize my problem and solution. What is TOP? Problem is that my detector could not track state of OpcodeStack, because stack becomes TOP. I cannot get elements in stack. if st\u2026","blog_url":"https://blog.kengo-toda.jp/","type":"rich","width":"100%","height":"190","image_url":null,"version":"1.0"}