Linux NFS development
 help / color / mirror / Atom feed
From: michael <michael@hq.newdream.net>
To: NFS List <nfs@lists.sourceforge.net>
Subject: more statd segfault
Date: Mon, 08 Sep 2003 12:58:53 -0700	[thread overview]
Message-ID: <3F5CDF7D.2070608@hq.newdream.net> (raw)

okay i have tracked down the segfault to here...

void
svc_getreqset (fd_set *readfds)
{
   register u_int32_t mask;
   register u_int32_t *maskp;
   register int setsize;
   register int sock;
   register int bit;

   setsize = _rpc_dtablesize ();
   maskp = (u_int32_t *) readfds->fds_bits;
   for (sock = 0; sock < setsize; sock += 32)
*    for (mask = *maskp++; (bit = ffs (mask)); mask ^= (1 << (bit - 1)))
       svc_getreq_common (sock + bit - 1);
}


the contents of the variables are as follows...
358     in svc.c
(gdb) print *maskp
$13 = 128
(gdb) print mask
$14 = 3221224588
(gdb) print setsize
$15 = 1048566
(gdb) print bit
$16 = 1048566
(gdb) print *readfds
$17 = {fds_bits = {128, 0 <repeats 31 times>}}
(gdb) n 10000

Program received signal SIGSEGV, Segmentation fault.
0x40112e3a in svc_getreqset (readfds=0xbffffc0c) at svc.c:359
359     in svc.c
(gdb) print sock
$37 = 8096
(gdb) print setsize
$38 = 1048566
(gdb) print bit
$39 = -1073741824
(gdb) print maskp
$40 = (u_int32_t *) 0xc0000000
(gdb) print *maskp
Cannot access memory at address 0xc0000000
(gdb)








-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

             reply	other threads:[~2003-09-09  1:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-08 19:58 michael [this message]
2003-09-12  2:05 ` more statd segfault michael
2003-09-12  6:39   ` Neil Brown
2003-09-12 20:21     ` Dan Kegel

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=3F5CDF7D.2070608@hq.newdream.net \
    --to=michael@hq.newdream.net \
    --cc=nfs@lists.sourceforge.net \
    /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