From: Andreas Hartmann <andihartmann@01019freenet.de>
To: linux-kernel@vger.kernel.org
Subject: ksymoops 2.4.10 segfaults
Date: Sat, 08 Jan 2005 12:01:57 +0100 [thread overview]
Message-ID: <croej5$5b8$1@pD9F86D6F.dip0.t-ipconnect.de> (raw)
Hello,
ksymoops segfaults in object.c while computing cmd_strlen, because
options->target is defined 'null':
/* Extract all symbols definitions from an object using nm */
static void read_nm_symbols(SYMBOL_SET *ss, const char *file, const
OPTIONS *options)
{
FILE *f;
char *cmd, *line = NULL, **string = NULL;
int i, cmd_strlen, size = 0;
static char const procname[] = "read_nm_symbols";
static char const nm_options[] = "--target=";
if (!regular_file(file, procname))
return;
printf ("Path to nm: %s\n",path_nm);
printf ("nm_options: %s\n",nm_options);
printf ("target: %s\n",(options->target));
printf ("file: %s\n",file);
cmd_strlen =
strlen(path_nm)+1+strlen(nm_options)+strlen(options->target)+1+strlen(file)+1;
printf ("length: %d\n",cmd_strlen);
cmd = malloc(cmd_strlen);
./ksymoops
ksymoops 2.4.10 on i686 2.4.29-pre3. Options used
-V (default)
-k /proc/ksyms (default)
-l /proc/modules (default)
-o /lib/modules/2.4.29-pre3/ (default)
-m /usr/src/linux/System.map (default)
Warning: You did not tell me where to find symbol information. I will
assume that the log matches the kernel and modules that are running
right now and I'll use the default options above for symbol resolution.
If the current kernel and/or modules do not match the log, you can get
more accurate output by telling me the kernel version and where to find
map, modules, ksyms etc. ksymoops -h explains the options.
Path to nm: /usr/local/bin/nm
nm_options: --target=
target: (null)
file: /lib-2.6/modules/2.4.29-pre3-swsusp/kernel/sound/pci/snd-via82xx.o
Segmentation fault (core dumped)
Kind regards,
Andreas Hartmann
next reply other threads:[~2005-01-08 11:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-08 11:01 Andreas Hartmann [this message]
2005-01-08 13:21 ` Keith Owens
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='croej5$5b8$1@pD9F86D6F.dip0.t-ipconnect.de' \
--to=andihartmann@01019freenet.de \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®