From: levi@localhost.nc3a.nato.int
To: levi@localhost.nc3a.nato.int
Cc: Maurice Lombardi <Maurice.Lombardi@ujf-grenoble.fr>,
adam.oldham@marconi.com, gdb@sources.redhat.com,
core@freepascal.org, gpc@gnu.de
Subject: Re: GDB scope does not work quite right for Pascal
Date: Fri, 01 Feb 2002 04:29:00 -0000 [thread overview]
Message-ID: <3BC72AF5.4030809@cygnus.com> (raw)
In-Reply-To: <20011012130740.A15975@nevyn.them.org>
> On Fri, Oct 12, 2001 at 06:57:32PM +0200, Maurice Lombardi wrote:
>
>> > There are several remarks to that bug report:
>> > 1) I don't know at all how nested functions work in C
>> >Are they allowed?
>
>>
>>
>> AKAIK no, they are not allowed, and this is the root of the problem,
>> since gdb is written mainly by/for C programmers.
>
>
> They aren't allowed by standard C. GCC does in fact allow them,
> although their use isn't recommended. I think GDB's support for them
> is somewhat crusty.
The thread
http://sources.redhat.com/ml/gdb-patches/2001-07/msg00714.html is
probably relevant.
Following on Joel's strategy (Ada) the first thing needed is probably a
testcase so that people know the status of the underlying code
Andrew
WARNING: multiple messages have this Message-ID
From: Andrew Cagney <ac131313@cygnus.com>
To: Daniel Jacobowitz <drow@mvista.com>,
Pierre Muller <muller@cerbere.u-strasbg.fr>
Cc: Maurice Lombardi <Maurice.Lombardi@ujf-grenoble.fr>,
adam.oldham@marconi.com, gdb@sources.redhat.com,
core@freepascal.org, gpc@gnu.de
Subject: Re: GDB scope does not work quite right for Pascal
Date: Fri, 12 Oct 2001 10:40:00 -0000 [thread overview]
Message-ID: <3BC72AF5.4030809@cygnus.com> (raw)
Message-ID: <20011012104000.rvXnVvC4B8wWUamOBLwtttgbN6IHZr5dJgDSZ3lQzNc@z> (raw)
In-Reply-To: <20011012130740.A15975@nevyn.them.org>
> On Fri, Oct 12, 2001 at 06:57:32PM +0200, Maurice Lombardi wrote:
>
>> > There are several remarks to that bug report:
>> > 1) I don't know at all how nested functions work in C
>> >Are they allowed?
>
>>
>>
>> AKAIK no, they are not allowed, and this is the root of the problem,
>> since gdb is written mainly by/for C programmers.
>
>
> They aren't allowed by standard C. GCC does in fact allow them,
> although their use isn't recommended. I think GDB's support for them
> is somewhat crusty.
The thread
http://sources.redhat.com/ml/gdb-patches/2001-07/msg00714.html is
probably relevant.
Following on Joel's strategy (Ada) the first thing needed is probably a
testcase so that people know the status of the underlying code
Andrew
next prev parent reply other threads:[~2002-02-01 12:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20011012124403.21432.qmail@sourceware.cygnus.com>
2002-02-01 4:29 ` levi
2001-10-12 8:29 ` Pierre Muller
2001-10-12 9:58 ` Maurice Lombardi
2002-02-01 4:29 ` levi
2001-10-12 10:16 ` Daniel Jacobowitz
2002-02-01 4:29 ` levi [this message]
2001-10-12 10:40 ` Andrew Cagney
2002-02-01 4:29 ` levi
[not found] <A3E34B558F5CD211B4980008C7A4A99003883EC6@sparrow.gso.mcs.m arconi.com>
2002-02-01 4:29 ` levi
2001-10-12 16:38 ` Pierre Muller
2001-10-12 11:21 Oldham, Adam
2002-02-01 4:29 ` levi
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=3BC72AF5.4030809@cygnus.com \
--to=levi@localhost.nc3a.nato.int \
--cc=Maurice.Lombardi@ujf-grenoble.fr \
--cc=adam.oldham@marconi.com \
--cc=core@freepascal.org \
--cc=gdb@sources.redhat.com \
--cc=gpc@gnu.de \
/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