Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: Aleksandar Ristovski <aristovski@qnx.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [patch] Assert when 'break' with no arguments
Date: Tue, 14 Feb 2012 19:23:00 -0000	[thread overview]
Message-ID: <20120214185333.GB14803@adacore.com> (raw)
In-Reply-To: <jhe7kc$d91$1@dough.gmane.org>

> ChangeLog:
> 2012-02-14  Aleksandar Ristovski  <aristovski@qnx.com>
> 
>        * frame.c (find_frame_sal): Initialise sal->pspace field from
> frame data.
>        * stack.c (set_last_displayed_sal): Perform sanity check of the data
>        passed in, in particular, validate that PSPACE is not NULL if
> requesting
>        valid last_displayed_* data.
> 
> 
> Test suite ChangeLOg:
> 2012-02-14  Aleksandar Ristovski  <aristovski@qnx.com>
> 
>     * gdb.base/break-inline.exp: New test.
>     * gdb.base/break-inline.c: New test.

I haven't looked at the validity of the patch (Pedro has a better
understanding of this area, for instance), but I still noticed some
trivial deviations from the GNU Coding Standards.

Your ChangeLog entry, for instance. Lines should be folded at 70 chars
(hard limit is 80 chars). Other violations highlighted below:

> +      /* Set pspace with frame's pspace */

End the sentence with a period (and two spaces before the '*/').

> +  if (valid && pspace == NULL) {
> +	warning(_("Trying to set NULL pspace."));
> +  }

Wrong formatting for first and second line.

> +  if (valid && pspace == NULL)
> +	last_displayed_sal_valid = 0;

Ditto for the second line (indentation is 2 spaces).

>    last_displayed_symtab = symtab;
>    last_displayed_line = line;
> +
>  }

Why are you adding an empty line here?

> #   Copyright 2012 Free
> #   Software Foundation, Inc.

Missing (C), and please join the two lines. If you copied some of
the testcase from another testcase, then you need to preserve the
original copyright years, I think.

> /* This testcase is part of GDB, the GNU debugger.
> 
>    Copyright 2012 Free Software
>    Foundation, Inc.

Same as above, please add the missing (C).

> #include <stdio.h>
> static int g;
> static inline void foo(void)
> {
>   g = 42;
>   printf("%d\n", g);
> }
> int main(int argc, char *argv[])
> {
>   foo();
>   return g;
> }

Is there a way to trigger the same problem without the dependency
on stdio.h? Many systems do not provide it (bareboard). I would
think that all you need is to define a function that has the same
profile as printf, no?

-- 
Joel


  parent reply	other threads:[~2012-02-14 18:54 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-14 18:03 Aleksandar Ristovski
2012-02-14 18:53 ` Aleksandar Ristovski
2012-02-14 18:06   ` Aleksandar Ristovski
2012-02-14 19:23 ` Joel Brobecker [this message]
2012-02-14 20:09   ` Aleksandar Ristovski
2012-02-14 20:18     ` Alfred M. Szmidt
2012-02-14 22:37       ` Aleksandar Ristovski
2012-02-15 17:15         ` Tom Tromey
2012-02-15 20:06           ` Aleksandar Ristovski
2012-02-19 16:42             ` [commit] testsuite: Fix break-inline.exp with gdbserver Jan Kratochvil
2012-02-24 15:52         ` [patch] Assert when 'break' with no arguments Pedro Alves
2012-02-24 16:00           ` Aleksandar Ristovski
2012-02-24 16:09             ` Pedro Alves
2012-02-24 16:18               ` Aleksandar Ristovski
2012-02-24 17:16                 ` Pedro Alves

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=20120214185333.GB14803@adacore.com \
    --to=brobecker@adacore.com \
    --cc=aristovski@qnx.com \
    --cc=gdb-patches@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