From: Jim Blandy <jimb@red-bean.com>
To: gdb-patches@sources.redhat.com
Subject: Fwd: Obvious: doc fix for 'struct memrange' in tracepoints.c
Date: Sat, 19 Nov 2005 12:43:00 -0000 [thread overview]
Message-ID: <8f2776cb0511182045h5fe6b1a7ye0811b1bfaa74a59@mail.gmail.com> (raw)
In-Reply-To: <8f2776cb0511182044r7a653ae5w46f3f2a1ddcaeec7@mail.gmail.com>
---------- Forwarded message ----------
From: Jim Blandy <jimb@red-bean.com>
Date: Nov 18, 2005 8:44 PM
Subject: Re: Obvious: doc fix for 'struct memrange' in tracepoints.c
To: Michael Snyder <msnyder@redhat.com>
On 11/18/05, Michael Snyder <msnyder@redhat.com> wrote:
> (psssst... there's another one at line 1229...)
Days like this make me feel like a real professional.
gdb/ChangeLog:
2005-11-18 Jim Blandy <jimb@redhat.com>
* tracepoint.c (collect_symbol): Doc fix.
Index: gdb/tracepoint.c
===================================================================
RCS file: /cvs/src/src/gdb/tracepoint.c,v
retrieving revision 1.79
diff -c -p -r1.79 tracepoint.c
*** gdb/tracepoint.c 19 Nov 2005 01:23:26 -0000 1.79
--- gdb/tracepoint.c 19 Nov 2005 04:42:36 -0000
*************** collect_symbol (struct collection_list *
*** 1226,1232 ****
DEPRECATED_SYMBOL_NAME (sym), len,
tmp /* address */);
}
! add_memrange (collect, -1, offset, len); /* 0 == memory */
break;
case LOC_REGISTER:
case LOC_REGPARM:
--- 1226,1232 ----
DEPRECATED_SYMBOL_NAME (sym), len,
tmp /* address */);
}
! add_memrange (collect, -1, offset, len); /* -1 == memory */
break;
case LOC_REGISTER:
case LOC_REGPARM:
next prev parent reply other threads:[~2005-11-19 4:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-19 4:45 Jim Blandy
2005-11-19 5:26 ` Daniel Jacobowitz
2005-11-19 12:42 ` Jim Blandy
[not found] ` <437E89C1.7050104@redhat.com>
[not found] ` <8f2776cb0511182044r7a653ae5w46f3f2a1ddcaeec7@mail.gmail.com>
2005-11-19 12:43 ` Jim Blandy [this message]
2005-11-19 12:56 ` Fwd: " Eli Zaretskii
2005-11-20 5:44 ` Jim Blandy
2005-11-20 5:47 ` Eli Zaretskii
2005-11-21 5:10 ` Jim Blandy
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=8f2776cb0511182045h5fe6b1a7ye0811b1bfaa74a59@mail.gmail.com \
--to=jimb@red-bean.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