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

Michal Ludvig writes:
 > Hi Daniel, Elena and others,
 > this problem is still present in recent HEAD - could anyone who knows 
 > the internals of symbols handling and .debug_info please help me with 
 > fixing it, please? I tried to debug it myself but got quickly lost in 
 > all those symbols<->types<->other_types references and couldn't find 
 > where the problem originates.
 > 
 > Also pointing out the right direction where to look for the bug would 
 > help me a lot :-)
 > 
 > BTW I also filled a PR with a very nice number 1333 for this issue.
 > 
 > Thanks in advance!
 > 
 > Michal Ludvig

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.
Does the same happen for 386? Maybe comparing the two would help. If
the problem is in generic code you should see the error there too.  If
not, step the two side by side and see if the x86-64 does something
weird.

elena



 > 
 > Michal Ludvig told me that:
 > > Hi all,
 > > I have problems debugging the attached code (real.f) on AMD64 platform. 
 > > However the problem doesn't seem to be AMD64-related, but Dwarf2-related 
 > > instead and it only happens if it is compiled by the PGI fortran 
 > > compiler (beta is available for free download at www.pgroup.com/AMD64).
 > > 
 > > Debugging the 'real' binary on AMD64/Linux systems leads to GDB internal 
 > > error:
 > > 
 > > $ ../gdb real
 > > GNU gdb 2003-07-08-cvs
 > > Copyright 2003 Free Software Foundation, Inc.
 > > [...]
 > > This GDB was configured as "x86_64-unknown-linux-gnu"...
 > > (gdb) b hurdgy
 > > Breakpoint 1 at 0x4000113c: file real.f, line 8.
 > > (gdb) r
 > > Starting program: /tmp/gdbbuild/gdb/fortran/real
 > > 
 > > Breakpoint 1, hurdgy (xx=
 > > /ttt/64/gdb-head/gdb/utils.c:1058: internal-error: virtual memory 
 > > exhausted: can't allocate 4294967404 bytes.
 > > A problem internal to GDB has been detected,
 > > further debugging may prove unreliable.
 > > Quit this debugging session? (y or n) y
 > > 
 > > /ttt/64/gdb-head/gdb/utils.c:1058: internal-error: virtual memory 
 > > exhausted: can't allocate 4294967404 bytes.
 > > A problem internal to GDB has been detected,
 > > further debugging may prove unreliable.
 > > Create a core file of GDB? (y or n) n
 > > $
 > > 
 > > Something is wrong in parsing the Dwarf2 .debug_info section - 
 > > unfortunately I don't understand the GDB internals in this field.
 > > Could someone help me with it, please?
 > > 
 > > All relevant files (source, asm, binaries, cores) are available at:
 > > http://tmp.logix.cz/amd/fortran/
 > > 
 > > Thanks in advance for any help!
 > > 
 > > Michal Ludvig
 > > 
 > > 
 > > ------------------------------------------------------------------------
 > > 
 > >       real flat(10)
 > >       call hurdgy(flat, 10)
 > > 
 > >       end
 > > 
 > >       subroutine hurdgy(xx,i)
 > >       integer i
 > >       real xx(i)
 > >       end

  reply	other threads:[~2003-08-14 12:41 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 [this message]
2003-08-14 13:17     ` Michal Ludvig
2003-08-14 14:56       ` Michal Ludvig

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=16187.34103.759484.814559@localhost.redhat.com \
    --to=ezannoni@redhat.com \
    --cc=drow@mvista.com \
    --cc=gdb@sources.redhat.com \
    --cc=mludvig@suse.cz \
    /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).