From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21887 invoked by alias); 29 Jul 2014 20:20:51 -0000 Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org Received: (qmail 21876 invoked by uid 89); 29 Jul 2014 20:20:50 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-4.4 required=5.0 tests=AWL,BAYES_00,RP_MATCHES_RCVD,SPF_HELO_PASS,SPF_PASS autolearn=ham version=3.3.2 X-HELO: mx1.redhat.com Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES256-GCM-SHA384 encrypted) ESMTPS; Tue, 29 Jul 2014 20:20:47 +0000 Received: from int-mx13.intmail.prod.int.phx2.redhat.com (int-mx13.intmail.prod.int.phx2.redhat.com [10.5.11.26]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id s6TKKiXT026552 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Tue, 29 Jul 2014 16:20:44 -0400 Received: from host2.jankratochvil.net (ovpn-116-29.ams2.redhat.com [10.36.116.29]) by int-mx13.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id s6TKKfPV016165 (version=TLSv1/SSLv3 cipher=AES128-GCM-SHA256 bits=128 verify=NO); Tue, 29 Jul 2014 16:20:43 -0400 Date: Tue, 29 Jul 2014 20:27:00 -0000 From: Jan Kratochvil To: Joel Brobecker Cc: gdb-patches@sourceware.org Subject: Re: [patch] Display Fortran strings in backtraces Message-ID: <20140729202041.GA20569@host2.jankratochvil.net> References: <20140728214654.GA26290@host2.jankratochvil.net> <20140729200513.GA14672@adacore.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20140729200513.GA14672@adacore.com> User-Agent: Mutt/1.5.23 (2014-03-12) X-IsSubscribed: yes X-SW-Source: 2014-07/txt/msg00767.txt.bz2 On Tue, 29 Jul 2014 22:05:13 +0200, Joel Brobecker wrote: > Sorry, Jan. That seems to be counter-intuitive; strings are not > scalars... The intent of the setting is to avoid having super-long > parameter values drowning the list parameters. Strings can be pretty > long, so I think the current behavior matches my current expectation. In such case normal C 'char *' parameters also should not be printed. Length of fortran strings is limited exactly the same way like C 'char *' strings are: Breakpoint 2, f (s='foo01010101010101010101010101010101010101010101010101010101010101010101010101010101010101010101010101010101010101010101010101010101010101010101010101010101010101010101010101010101010101010101010101010'..., _s=203) at ./gdb.fortran/fortran-frame-string.f90:24^M (gdb) show print elements Limit on string chars or array elements to print is 200. What is the difference between Fortran strings and C 'char *' strings? Thanks, Jan