From @masak

<masak> moritz​: I think I've found a bug in the backtrace printer​:
https://gist.github.com/1343548
<moritz> masak​: yes, I know. But I don't think the backtrace printer is to blame
<masak> oh?
<moritz> masak​: I think the wrong file is come out wrongly out of the
backtrace annotations already
<masak> moritz​: but there's a fix, right?
<moritz> the handling of file names in Backtrace.pm is so trivial that
I'd be shocked if it were wrong
<masak> ok.
<masak> moritz​: as a bot, I'm confused by the above as to what to do.
would an RT ticket be beneficial, or just noise? as a developer, I
would much prefer for it to report the correct module -- I'm fine
with the error not being in code you wrote, as long as it's fixed
eventually.
<jnthn> masakbot submit rt
* masak submits rakudobug
<masak> whoa.
<masak> creepy.
<jnthn> ...works faster than p6eval

From @moritz

Fixed now. Writing a proper test for that will be fun :-)

The RT System itself - Status changed from 'new' to 'open'

From @moritz

Now tested in integration/error-reporting.t

@moritz - Status changed from 'open' to 'resolved'