From: "Peter.Schauer" <Peter.Schauer@regent.e-technik.tu-muenchen.de>
To: ezannoni@cygnus.com (Elena Zannoni)
Cc: gdb@sourceware.cygnus.com
Subject: Re: Problem with 2000-05-05 elfread.c change
Date: Tue, 03 Oct 2000 05:06:00 -0000 [thread overview]
Message-ID: <200010030955.LAA03533@reisser.regent.e-technik.tu-muenchen.de> (raw)
In-Reply-To: <14809.15857.439093.624776@kwikemart.cygnus.com>
I definitely think this has to be fixed for GDB 5.1 though.
> Peter.Schauer writes:
>
> I believe you. I was working on getting rid of that limit by
> allocating stuff dynamically for the sections, but I didn't finish
> it. Maybe I can find some time soon to finish it, but cannot guarantee
> it. I'll see what I can do.
> The change in elfread.c is however necessary to fix other problems.
>
> Sorry.
>
> Elena
--
Peter Schauer pes@regent.e-technik.tu-muenchen.de
next prev parent reply other threads:[~2000-10-03 5:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-10-02 10:04 Peter.Schauer
2000-10-02 19:01 ` Elena Zannoni
2000-10-03 5:06 ` Peter.Schauer [this message]
2000-10-03 18:44 ` Elena Zannoni
2000-10-04 4:00 ` CVS GDB and Register Numbers and Remote Protocol Steven Johnson
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=200010030955.LAA03533@reisser.regent.e-technik.tu-muenchen.de \
--to=peter.schauer@regent.e-technik.tu-muenchen.de \
--cc=ezannoni@cygnus.com \
--cc=gdb@sourceware.cygnus.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).