From: Petr Vandrovec <vandrove@vc.cvut.cz>
To: torvalds@transmeta.com
Cc: ak@suse.de, linux-kernel@vger.kernel.org
Subject: [PATCH] kallsyms prints wrong symbol names
Date: Thu, 9 Jan 2003 22:58:21 +0100 [thread overview]
Message-ID: <20030109215821.GA2935@vana> (raw)
Hi Linus,
Since stem compression arrived to kallsyms table, we are printing
name of symbol BEFORE one we want to print (and empty string for
first symbol) because of we return buffer with copy of last name
we skipped instead of 'name' variable as we did before. So one more
pass through loop is required.
Without this patch my stack traces were really strange...
Thanks,
Petr Vandrovec
vandrove@vc.cvut.cz
--- linux-2.5.55/kernel/kallsyms.c 2003-01-09 22:47:40.000000000 +0100
+++ linux-2.5.55/kernel/kallsyms.c 2003-01-09 22:38:01.000000000 +0100
@@ -46,7 +46,7 @@
}
/* Grab name */
- for (i = 0; i < best; i++) {
+ for (i = 0; i < best + 1; i++) {
unsigned prefix = *name++;
strncpy(namebuf + prefix, name, 127 - prefix);
name += strlen(name) + 1;
reply other threads:[~2003-01-09 21:50 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20030109215821.GA2935@vana \
--to=vandrove@vc.cvut.cz \
--cc=ak@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.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;
as well as URLs for NNTP newsgroup(s).