{"action":"created","issue":{"url":"https://api.github.com/repos/dropbox/pyston/issues/690","labels_url":"https://api.github.com/repos/dropbox/pyston/issues/690/labels{/name}","comments_url":"https://api.github.com/repos/dropbox/pyston/issues/690/comments","events_url":"https://api.github.com/repos/dropbox/pyston/issues/690/events","html_url":"https://github.com/dropbox/pyston/issues/690","id":94361674,"number":690,"title":"Python stacktraces with a GC call involved should indicate the presence of the GC call","user":{"login":"rudi-c","id":2747897,"avatar_url":"https://avatars.githubusercontent.com/u/2747897?v=3","gravatar_id":"","url":"https://api.github.com/users/rudi-c","html_url":"https://github.com/rudi-c","followers_url":"https://api.github.com/users/rudi-c/followers","following_url":"https://api.github.com/users/rudi-c/following{/other_user}","gists_url":"https://api.github.com/users/rudi-c/gists{/gist_id}","starred_url":"https://api.github.com/users/rudi-c/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/rudi-c/subscriptions","organizations_url":"https://api.github.com/users/rudi-c/orgs","repos_url":"https://api.github.com/users/rudi-c/repos","events_url":"https://api.github.com/users/rudi-c/events{/privacy}","received_events_url":"https://api.github.com/users/rudi-c/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":1,"created_at":"2015-07-10T18:13:28Z","updated_at":"2015-11-19T08:39:38Z","closed_at":null,"body":"Consider the following stacktrace tail:\r\n\r\n```\r\n  File \"/home/vagrant/pyston-build-dbg/from_cpython/Lib/sre_parse.py\", line 203, in get:\r\n    self.__next()\r\n  File \"/home/vagrant/pyston-build-dbg/from_cpython/Lib/sre_parse.py\", line 193, in __next:\r\n    self.index = self.index + len(char)\r\n  File \"/home/vagrant/pyston-build-dbg/from_cpython/Lib/codecs.py\", line \r\n629, in __getattr__:\r\n    return getattr(self.stream, name)\r\n```\r\n\r\n\r\n(193) has no obvious relation to (629). What's happening is that in (193), a BoxedInt is allocating, causing a GC call, causing a finalizer call, causing an attribute lookup for `\"__del__\"`.\r\n\r\nSomething like this would be nice:\r\n\r\n```\r\n  File \"/home/vagrant/pyston-build-dbg/from_cpython/Lib/sre_parse.py\", line 203, in get:\r\n    self.__next()\r\n  File \"/home/vagrant/pyston-build-dbg/from_cpython/Lib/sre_parse.py\", line 193, in __next:\r\n    self.index = self.index + len(char)\r\n(... garbage collection ...)\r\n  File \"/home/vagrant/pyston-build-dbg/from_cpython/Lib/codecs.py\", line \r\n629, in __getattr__:\r\n    return getattr(self.stream, name)\r\n```\r\n"},"comment":{"url":"https://api.github.com/repos/dropbox/pyston/issues/comments/157989934","html_url":"https://github.com/dropbox/pyston/issues/690#issuecomment-157989934","issue_url":"https://api.github.com/repos/dropbox/pyston/issues/690","id":157989934,"user":{"login":"rudi-c","id":2747897,"avatar_url":"https://avatars.githubusercontent.com/u/2747897?v=3","gravatar_id":"","url":"https://api.github.com/users/rudi-c","html_url":"https://github.com/rudi-c","followers_url":"https://api.github.com/users/rudi-c/followers","following_url":"https://api.github.com/users/rudi-c/following{/other_user}","gists_url":"https://api.github.com/users/rudi-c/gists{/gist_id}","starred_url":"https://api.github.com/users/rudi-c/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/rudi-c/subscriptions","organizations_url":"https://api.github.com/users/rudi-c/orgs","repos_url":"https://api.github.com/users/rudi-c/repos","events_url":"https://api.github.com/users/rudi-c/events{/privacy}","received_events_url":"https://api.github.com/users/rudi-c/received_events","type":"User","site_admin":false},"created_at":"2015-11-19T08:39:38Z","updated_at":"2015-11-19T08:39:38Z","body":"This issue is slightly out of date, as we no longer call finalizers from inside a garbage collection pass. They are put in a pending finalization list, which can get called at arbitrary points in the program (equally confusing). So a line saying (...calling finalizers...) would be helpful."}}