Hello everybody. I'm in a weird case. I'm trying to debug some code but my debugger never stops at f...

# android

[cucharro]

Hello everybody. I'm in a weird case. I'm trying to debug some code but my debugger never stops at finally blocks, does anyone knows why? To me the finally block should be reached all the time, right?

[Robert Menke]

Are you returning from your try or catch blocks?

[cucharro]

in some lines yes, others no

[cucharro]

but none stops at finally

[cucharro]

and AS, shows the alert "no executable code" at finally blocks

[Kris Wong]

there has to be a little checkmark on the BP when you're running

[cucharro]

yes

[Kris Wong]

unfortunately the debugger has never been top notch

[louiscad]

Do you have actual code in that finally block? You'll need to put the breakpoint on a line having this actual code, I don't think lines where the finally keyword is the only code can have breakpoints (the IDE shows you a checkmark or a stop mark to tell you about it once the class is loaded)

[cucharro]

I tried that, but when running code that stop (circle with cross line) is shown

[cucharro]

yes there is code, I'll share a print

[Robert Menke]

So if you’re returning before finally it will never get executed

[louiscad]

@Robert Menke Wrong: finally is always executed after the return expression, just before the value is actually returned.

[louiscad]

Unless you didn't enter the corresponding try block of course.

[cucharro]

image.png

[cucharro]

this is how it looks

[Kris Wong]

have to ask the obvious question... you're sure you built and ran after adding that line?

[Robert Menke]

@louiscad 🤦‍♂️ Oh man I never use it like that. Just had to try it out in the editor. Kind of unintuitive tbh.

[Robert Menke]

thanks for the correction

[Kris Wong]

seems pretty intuitive to me 😛

[cucharro]

Yes, I did @Kris Wong. I'm doing it right now 😛

[Kris Wong]

that's quite strange then

[cucharro]

It just don't stop at the line

[Kris Wong]

is that function inlined and empty?

[cucharro]

no, it is a regular one

[Kris Wong]

i'm out of ideas

[cucharro]

I'll print a logcat message just to check if the code running. This is first time I'm through that

[cucharro]

it's running. Look like it is an AS bug

[cucharro]

thank you everybody for the help

[louiscad]

Look in the gutter @cucharro: there's a barred sign meaning it couldn't find the corresponding line of code deployed on the device! You can try running the app again, and make sure you don't edit the code afterwards, as this will otherwise shift the code line numbers and deployed code under debugging would be out of sync with code in IDE, putting in at risk to encounter the same issue again.

[Robert Menke]

I mean it doesn’t seem intuitive to me that finally intercepts a return in a try block.

fun foo(): String {
        try {
            return "hello"
        }
        finally {
            return "world"
        }
    }

but I suppose it makes sense

[louiscad]

@Robert Menke It's very useful to unregister listeners/callbacks with coroutines. Also, almost no one uses the return keyword in a finally block.

[Robert Menke]

Ya I see the utility. Tbh though I’d prefer something like Go or Swift’s defer keyword for that.

[louiscad]

But I just learned thanks to you it works the intuitive way: finally wins.

[louiscad]

defer means something entirely different to me

[louiscad]

async from kotlinx.coroutines returns Deferred<T>