> I think you're getting an end user's-eye view of what internal backtraces > look like.
Right! If the problem is simply a user error, (an invalid entry in an sprintf format string), the messages are irrelevant and confusing. I thought I was reporting some problem in the processing or creation of the error message. In that case P6 is broken in some way, and the messages presumably help the language's developers fix that. On 8/27/16, Brandon Allbery via RT <perl6-bugs-follo...@perl.org> wrote: > On Sat, Aug 27, 2016 at 4:22 PM, Timo Paulssen <t...@wakelift.de> wrote: > >> are you aware that that's just the filename? and the whole thing is just >> the backtrace that shows where things are going wrong? >> > > I think you're getting an end user's-eye view of what internal backtraces > look like. (Yes, really. See this in MacPorts support too; it errs on the > side of providing copious detail in its logfiles.) > > -- > brandon s allbery kf8nh sine nomine > associates > allber...@gmail.com > ballb...@sinenomine.net > unix, openafs, kerberos, infrastructure, xmonad > http://sinenomine.net > >
