Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: levi@localhost.nc3a.nato.int
To: levi@localhost.nc3a.nato.int
Cc: Pierre Muller <muller@cerbere.u-strasbg.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: <20011012130740.A15975@nevyn.them.org> (raw)
In-Reply-To: <3BC720FC.90101@ujf-grenoble.fr>

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.


-- 
Daniel Jacobowitz                           Carnegie Mellon University
MontaVista Software                         Debian GNU/Linux Developer



WARNING: multiple messages have this Message-ID
From: Daniel Jacobowitz <drow@mvista.com>
To: Maurice Lombardi <Maurice.Lombardi@ujf-grenoble.fr>
Cc: Pierre Muller <muller@cerbere.u-strasbg.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:16:00 -0000	[thread overview]
Message-ID: <20011012130740.A15975@nevyn.them.org> (raw)
Message-ID: <20011012101600.XLpxbEvMYoSuoNOZny7yrCtViRcAgSkEDkA7_CXftr8@z> (raw)
In-Reply-To: <3BC720FC.90101@ujf-grenoble.fr>

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.


-- 
Daniel Jacobowitz                           Carnegie Mellon University
MontaVista Software                         Debian GNU/Linux Developer


  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
2002-02-01  4:29     ` levi [this message]
2001-10-12 10:16       ` Daniel Jacobowitz
2002-02-01  4:29       ` levi
2001-10-12 10:40         ` Andrew Cagney
     [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=20011012130740.A15975@nevyn.them.org \
    --to=levi@localhost.nc3a.nato.int \
    --cc=adam.oldham@marconi.com \
    --cc=core@freepascal.org \
    --cc=gdb@sources.redhat.com \
    --cc=gpc@gnu.de \
    --cc=muller@cerbere.u-strasbg.fr \
    /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