public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: Andrew Burgess <aburgess@broadcom.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [PATCH] Disassemble over end of line table sequence.
Date: Mon, 31 Jan 2011 03:14:00 -0000	[thread overview]
Message-ID: <20110131024148.GA29739@adacore.com> (raw)
In-Reply-To: <4D357E8D.3040304@broadcom.com>

> gdb/ChangeLog
> 
> 2011-01-18  Andrew Burgess  <aburgess@broadcom.com>
> 
> 	* disasm.c (compare_lines): Handle the end of sequence markers
> 	within the line table to better support disassembling over
> 	compilation unit boundaries.
> 
> gdb/testsuite/ChangeLog
> 
> 2011-01-18  Andrew Burgess  <aburgess@broadcom.com>
> 
> 	* gdb.base/disasm-end-cu-1.c, gdb.base/disasm-end-cu-2.c,
> 	gdb.base/disasm-end-cu.exp: New test for disassembling over the
> 	boundary between two compilation units.

Sorry for the late review.  For some reason, I completely missed this
email.  Thanks for pinging.

I think we're almost there.  The disasm.c change looks good to me.
But I still have a couple of requests for the testcase.

> +   You should have received a copy of the GNU General Public License
> +   along with this program.  If not, see <http://www.gnu.org/licenses/>.  */
> +
> +#include <stdio.h>

Can you make your testcase not depend on stdio.h? IO is not always
available, particularly on bareboard targets, so it'd be nice to be
able to build the example on these platforms too... This should be easily
doable by just having another unit that provides a function with the
same signature.

> +# This test tries to disassemble over the boundary between two compilation
> +# units displaying source lines. This checks that the disassemble routine
> +# can handle our use of line number 0 to mark the end of sequence.

Just a nit: missing second space after the period on the second line.

> +gdb_test_multiple "disassemble /m ${main_addr},${dummy_3_addr}" "Disassemble address range with source" {
[...]
> +    timeout {
> +        fail "(timeout) waiting for output of disassemble command"

The "timeout" branch is unnecessary (it's already handled by
gdb_test_multiple).

-- 
Joel

  parent reply	other threads:[~2011-01-31  2:42 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-15 14:24 Andrew Burgess
2011-01-13 11:47 ` Andrew Burgess
2011-01-15  7:56   ` Doug Evans
2011-01-14 16:30 ` Joel Brobecker
2011-01-18 15:20   ` Andrew Burgess
2011-01-25 17:45     ` Andrew Burgess
2011-01-31  3:14     ` Joel Brobecker [this message]
2011-02-02 19:17       ` Andrew Burgess
2011-02-03  5:02         ` Joel Brobecker
2011-02-03 14:47           ` [PATCH] [COMMIT] " Andrew Burgess

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=20110131024148.GA29739@adacore.com \
    --to=brobecker@adacore.com \
    --cc=aburgess@broadcom.com \
    --cc=gdb-patches@sourceware.org \
    /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).