Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Jim Blandy" <jimb@red-bean.com>
To: "Jim Blandy" <jimb@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: expand-symtabs.exp
Date: Mon, 28 Jan 2008 04:18:00 -0000	[thread overview]
Message-ID: <8f2776cb0801271426w7c5cedf9n773f86aa8823dc18@mail.gmail.com> (raw)
In-Reply-To: <m3ve5fb2wh.fsf@codesourcery.com>

"Dependings"?

gdb/testsuite/ChangeLog:
2008-01-27  Jim Blandy  <jimb@codesourcery.com>

	* gdb.base/expand-psymtabs.exp: Doc fix to the doc fix.

Index: gdb/testsuite/gdb.base/expand-psymtabs.exp
===================================================================
RCS file: /cvs/src/src/gdb/testsuite/gdb.base/expand-psymtabs.exp,v
retrieving revision 1.3
diff -u -r1.3 expand-psymtabs.exp
--- gdb/testsuite/gdb.base/expand-psymtabs.exp	27 Jan 2008 17:19:06 -0000	1.3
+++ gdb/testsuite/gdb.base/expand-psymtabs.exp	27 Jan 2008 22:24:19 -0000
@@ -26,7 +26,7 @@
 # different preprocessor symbols #defined; the first .o only has
 # 'main' at some earlier source lines, while the second .o only has
 # 'foo' at later source lines.  So when setting breakpoints by line
-# number, which full symtab we need dependings on the line number in
+# number, which full symtab we need depends on the line number in
 # question.
 #
 # This test is meant to verify that, even with lazy partial symtab


      parent reply	other threads:[~2008-01-27 22:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200801271528.m0RFSMo6032355@brahms.sibelius.xs4all.nl>
2008-01-27 18:08 ` expand-symtabs.exp Jim Blandy
2008-01-27 22:27   ` expand-symtabs.exp Mark Kettenis
2008-01-28 17:19     ` expand-symtabs.exp Carlos Eduardo Seo
2008-01-28 20:00     ` expand-symtabs.exp Jim Blandy
2008-01-28  4:18   ` Jim Blandy [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=8f2776cb0801271426w7c5cedf9n773f86aa8823dc18@mail.gmail.com \
    --to=jimb@red-bean.com \
    --cc=gdb-patches@sourceware.org \
    --cc=jimb@codesourcery.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