Project

General

Profile

Actions
Copy link

Bug #18743

closed

Enumerator#next / peek re-use each others stacktraces

Bug #18743: Enumerator#next / peek re-use each others stacktraces

Added by sos4nt (Stefan Schüßler) over 3 years ago. Updated over 1 year ago.

Status:
Closed
Assignee:
ko1 (Koichi Sasada)
Target version:
-
ruby -v:
Backport:
3.0: REQUIRED, 3.1: REQUIRED, 3.2: DONE
[ruby-core:108294]

Description

I encountered an odd behavior.

If I rescue the StopIteration exception from peek and call next afterwards: (or vice-versa)

# enum.rb # 1 # 2 enum = [].each # 3 enum.peek rescue nil # 4 enum.next # 5

it will show the stacktrace from the rescued peek call:

$ ruby enum.rb enum.rb:4:in `peek': iteration reached an end (StopIteration)	from enum.rb:4:in `<main>'

Whereas the error should refer to next on line number 5.

The same happens when calling peek after next or when having muliple peek / next calls:

# enum.rb # 1 # 2 enum = [].each # 3 enum.peek rescue nil # 4 enum.next rescue nil # 5 enum.peek rescue nil # 6 puts "line #{__LINE__}" # 7 enum.next # 8

The stacktrace from the first (rescued) peek or next call will be shown which doesn't reflect the actual error location:

$ ruby enum.rb line 7 enum.rb:4:in `peek': iteration reached an end (StopIteration)	from enum.rb:4:in `<main>'

This is very confusing when debugging code.

Files

01-Recreate-stacktrace-enumerator.patch (1.29 KB) 01-Recreate-stacktrace-enumerator.patch marcper (Marcelo Pereira), 10/23/2022 01:09 PM
Actions
Copy link

Also available in: PDF Atom