Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@is.elta.co.il>
To: Daniel Berlin <dan@cgsoftware.com>
Cc: Andrew Cagney <ac131313@cygnus.com>,
	GDB Discussion <gdb@sources.redhat.com>
Subject: Re: 5.1 NEWS
Date: Mon, 09 Jul 2001 01:31:00 -0000	[thread overview]
Message-ID: <Pine.SUN.3.91.1010709112213.6368O@is> (raw)
In-Reply-To: <877kxir11l.fsf@cgsoftware.com>

On Mon, 9 Jul 2001, Daniel Berlin wrote:

> > Clear and concise bug reports might help solve whatever problems you
> > see.
> Thanks for the hint. Again.

Sorry, given the lack of response to the previous hint, I thought my 
message got lost.

> However, you speak of it as if these were a few isolated problems.
> They weren't.
> You get hit with them attempting to debug any pascal program, right
> from the get go (this is a pascal program i had compiled last time i
> tried this):

I don't even know what Pascal compiler did Pierre use for testing the 
current support (was it really gpc?), so I cannot judge the problems you 
present.

> (from p-exp.y, at the top)
>     - pascal string operations are not supported at all.
>     - there are some problems with boolean types.
>     - Pascal type hexadecimal constants are not supported
>       because they conflict with the internal variables format.
>    Probably also lots of other problems, less well defined PM */
> These are *serious* limitations.

Not unlike many others in GDB.  Problems with shared libraries, 
multi-threading, and C++ come to mind.

> I'm also curious as to why I have to go to great lengths to prove
> this.

Because you know something others don't.  For example, I never use 
Pascal, so I don't have time to read Pascal-related files in GDB.  For 
the same reason, you probably don't know much about limitations of GDB in 
the DJGPP port, so it's up to me to ``go to great lengths'' in order to 
explain them, should that become an issue (as it happened a few times).


      reply	other threads:[~2001-07-09  1:31 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-07 10:23 Andrew Cagney
2001-07-07 11:11 ` Daniel Berlin
2001-07-08  1:18   ` Eli Zaretskii
2001-07-08 19:43   ` Andrew Cagney
2001-07-08 22:06     ` Daniel Berlin
2001-07-09  0:03       ` Eli Zaretskii
2001-07-09  0:53         ` Daniel Berlin
2001-07-09  1:31           ` Eli Zaretskii [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=Pine.SUN.3.91.1010709112213.6368O@is \
    --to=eliz@is.elta.co.il \
    --cc=ac131313@cygnus.com \
    --cc=dan@cgsoftware.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