public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Michal Ludvig <mludvig@suse.cz>
To: gdb <gdb@sources.redhat.com>
Cc: Elena Zannoni <ezannoni@redhat.com>, Daniel Jacobowitz <drow@mvista.com>
Subject: Re: Dwarf2-related Internal error
Date: Thu, 14 Aug 2003 14:56:00 -0000	[thread overview]
Message-ID: <3F3BA318.3050305@suse.cz> (raw)
In-Reply-To: <3F3B8C04.1010309@suse.cz>

Michal Ludvig told me that:
> Elena Zannoni told me that:
> 
>> I don't have much time to devote to this, but usually that kind of
>> error is generated by some infinite loop that gdb got itself into.
> 
> 
> Unlikely. The immediate problem is that the size of function's parameter 
> 'xx' is too big:
> 
> (top-gdb) f
> #0  read_var_value (var=0x8b35c0, frame=0x85ad98)
>     at ../../gdb-head/gdb/findvar.c:397
> 397       struct type *type = SYMBOL_TYPE (var);
> (top-gdb) p *var->type
> $2 = {pointer_type = 0x0, reference_type = 0x0, chain = 0x89fc00,
>   instance_flags = 0, length = 4294967292, main_type = 0x89fc28}
> (top-gdb) p (int)4294967292
> $3 = -4
> (top-gdb)
> 
> Very likely it was ment to be -4 because something somewhere in the 
> debug info was wrongly interpreted.

OK, I have found the problem. The type of the parameter 'xx' is an array 
with unspecified size. Lower bound is set to '1' for Fortran and since 
there is no upper bound specified, it's set to '-1' by default.

3097     else if (attr->form == DW_FORM_block1)
3098     {
3099       /* GCC encodes arrays with unspecified or dynamic length
3100          with a DW_FORM_block1 attribute.
3101          FIXME: GDB does not yet know how to handle dynamic
3102          arrays properly, treat them as arrays with unspecified
3103          length for now.  */
3104       high = -1;
3105     }

Later, when the actual size of the array type is computed, it takes the 
size of the main type (real, size=4) and multiplies it by 
(high-low+1=-1) leading to -4 which is quite a big number when converted 
to unsigned.

Now how to solve it. For now I did

                      length for now.  */
                   high = -1;
+                 if (cu_language == language_fortran)
+                   high = 0;
                 }

which at least prevents GDB from crashing. IMHO it achieves the same 
behaviour as for other languages, where low=0, high=-1 and so the size 
of the array results to 0. In fortran low=1, so with high=0 the size 
will become 0 as well.

Would this be an acceptable solution? Any comments?

Michal Ludvig
-- 
* SuSE CR, s.r.o     * mludvig@suse.cz
* (+420) 296.545.373 * http://www.suse.cz

      reply	other threads:[~2003-08-14 14:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-08 14:36 Michal Ludvig
2003-08-14 11:03 ` Michal Ludvig
2003-08-14 12:41   ` Elena Zannoni
2003-08-14 13:17     ` Michal Ludvig
2003-08-14 14:56       ` Michal Ludvig [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3F3BA318.3050305@suse.cz \
    --to=mludvig@suse.cz \
    --cc=drow@mvista.com \
    --cc=ezannoni@redhat.com \
    --cc=gdb@sources.redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).