From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Original-To: poffice@blade.nagaokaut.ac.jp Delivered-To: poffice@blade.nagaokaut.ac.jp Received: from kankan.nagaokaut.ac.jp (kankan.nagaokaut.ac.jp [133.44.2.24]) by blade.nagaokaut.ac.jp (Postfix) with ESMTP id 708851960244 for ; Mon, 13 Jul 2015 23:05:58 +0900 (JST) Received: from funfun.nagaokaut.ac.jp (funfun.nagaokaut.ac.jp [133.44.2.201]) by kankan.nagaokaut.ac.jp (Postfix) with ESMTP id C0E3BB5D8C6 for ; Mon, 13 Jul 2015 23:34:06 +0900 (JST) Received: from funfun.nagaokaut.ac.jp (localhost.nagaokaut.ac.jp [127.0.0.1]) by funfun.nagaokaut.ac.jp (Postfix) with ESMTP id 8806E97A854 for ; Mon, 13 Jul 2015 23:34:09 +0900 (JST) X-Virus-Scanned: amavisd-new at nagaokaut.ac.jp Authentication-Results: funfun.nagaokaut.ac.jp (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=sendgrid.me Received: from funfun.nagaokaut.ac.jp ([127.0.0.1]) by funfun.nagaokaut.ac.jp (funfun.nagaokaut.ac.jp [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 12OAaO0ONMvG for ; Mon, 13 Jul 2015 23:34:09 +0900 (JST) Received: from voscc.nagaokaut.ac.jp (voscc.nagaokaut.ac.jp [133.44.1.100]) by funfun.nagaokaut.ac.jp (Postfix) with ESMTP id 4C95697A82C for ; Mon, 13 Jul 2015 23:34:09 +0900 (JST) Received: from neon.ruby-lang.org (neon.ruby-lang.org [221.186.184.75]) by voscc.nagaokaut.ac.jp (Postfix) with ESMTP id 547B995243E for ; Mon, 13 Jul 2015 23:34:06 +0900 (JST) Received: from [221.186.184.76] (localhost [IPv6:::1]) by neon.ruby-lang.org (Postfix) with ESMTP id CA7FE120443; Mon, 13 Jul 2015 23:34:06 +0900 (JST) X-Original-To: ruby-core@ruby-lang.org Delivered-To: ruby-core@ruby-lang.org Received: from o2.heroku.sendgrid.net (o2.heroku.sendgrid.net [67.228.50.55]) by neon.ruby-lang.org (Postfix) with ESMTPS id 4660512043B for ; Mon, 13 Jul 2015 23:34:03 +0900 (JST) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sendgrid.me; h=from:to:references:subject:mime-version:content-type:content-transfer-encoding:list-id; s=smtpapi; bh=746UViciELJwseKJs1wlZuCqYLw=; b=cveUHcRF8Vqw9cDAcl NkYDUZizk4qLfIKZBgTEF33JrtQB/e0+IhAdvT/vcjNxb1uNbWQZp1aWQO4Xucti nfnwvPgeySdhszgaonpNEPOQWtQ+AcHPb7s9Mr1RjNub7MJdzpIFfH7GT2JERNVL 8lGVv/dVPMDThoLsKHfe4Qn8U= Received: by filter0459p1mdw1.sendgrid.net with SMTP id filter0459p1mdw1.28867.55A3CC5227 2015-07-13 14:33:56.032007517 +0000 UTC Received: from herokuapp.com (ec2-54-90-158-79.compute-1.amazonaws.com [54.90.158.79]) by ismtpd-046 (SG) with ESMTP id 14e87d62738.6f38.c600c3 for ; Mon, 13 Jul 2015 14:33:55 +0000 (UTC) Date: Mon, 13 Jul 2015 14:33:55 +0000 From: nobu@ruby-lang.org To: ruby-core@ruby-lang.org Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Redmine-MailingListIntegration-Message-Ids: 44579 X-Redmine-Project: ruby-trunk X-Redmine-Issue-Id: 11347 X-Redmine-Issue-Author: akostadinov X-Redmine-Sender: nobu X-Mailer: Redmine X-Redmine-Host: bugs.ruby-lang.org X-Redmine-Site: Ruby Issue Tracking System X-Auto-Response-Suppress: All Auto-Submitted: auto-generated X-SG-EID: ync6xU2WACa70kv/Ymy4QrNMhiuLXJG8OTL2vJD1yS7CsVpfrbI6L0W+F6XVauZ8HeG3mlh102be8q JzuI69371zzwiodOM2MaSLFMcEWkW4XR3/fVNJO99ZeJx5d8LdpFbmKlnOAzWXGub69xzBWnlfsstZ 09Z/USbz6PAGsaC653Zh7c5SVqNE5XBL2SnI X-ML-Name: ruby-core X-Mail-Count: 69958 Subject: [ruby-core:69958] [Ruby trunk - Feature #11347] Errors with cause not reported properly to console X-BeenThere: ruby-core@ruby-lang.org X-Mailman-Version: 2.1.15 Precedence: list Reply-To: Ruby developers List-Id: Ruby developers List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: ruby-core-bounces@ruby-lang.org Sender: "ruby-core" Issue #11347 has been updated by Nobuyoshi Nakada. Tracker changed from Bug to Feature Description updated ---------------------------------------- Feature #11347: Errors with cause not reported properly to console https://bugs.ruby-lang.org/issues/11347#change-53390 * Author: Aleksandar Kostadinov * Status: Open * Priority: Normal * Assignee: ---------------------------------------- Hello, errors with `cause` are an important and very useful feature for debugging. It seems though default reporting is not showing the `cause` and nested causes to user. Here's a test file: ~~~ruby raise "GAHGAH" rescue raise "error with cause" rescue e=$! puts "Error: #{e}" puts "Cause: #{e.cause}" raise e ~~~ As you can see, the `cause` of the error is not printed in any way to the console when error is raised: ~~~ $ ruby /tmp/test.rb Error: error with cause Cause: GAHGAH /tmp/test.rb:1:in `rescue in
': error with cause (RuntimeError) from /tmp/test.rb:1:in `
~~~ -- https://bugs.ruby-lang.org/