From: Jim Davis <jdavis@CS.Arizona.EDU>
To: Kevin Coffman <kwc@citi.umich.edu>
Cc: nfs@lists.sourceforge.net
Subject: Re: rpc.gssd segfault on FC5 client
Date: Mon, 29 Jan 2007 16:34:35 -0700 [thread overview]
Message-ID: <45BE848B.2030907@CS.Arizona.EDU> (raw)
In-Reply-To: <4d569c330701291518q5ece6beeoebff95c2ba44c3b7@mail.gmail.com>
Kevin Coffman wrote:
> On 1/29/07, Jim Davis <jdavis@cs.arizona.edu> wrote:
>> Kevin Coffman wrote:
>> > I'm not seeing nfs-utils-debuginfo available. What is included with
>> > nfs-utils-debuginfo-1.0.8.rc2-4.FC5.2 ?
>>
>> Oh, right, I downloaded that rpm to another system and tarred the
>> contents across to this one. (That system had the same problem but I
>> decided to focus on just this one.) The rpm is supposed to have
>> debuggable versions of the nfs-utils in it:
>
> So it looks like running /usr/lib/debug/usr/sbin/rpc.gssd.debug might
> give us a backtrace to work with?
Well, I'm not really clear on how the debuginfo stuff is supposed to be
used, but it doesn't seem that I can run that file directly. The best I
could come up with after googling around is that it's meant to fed to
gdb to analyze core dumps from the real executable. But it's quite
possible I'm missing something there...
sh-3.1# ls -l /usr/lib/debug/usr/sbin/rpc.gssd.debug
-rwxr-xr-x 1 root root 60564 Feb 12 2006
/usr/lib/debug/usr/sbin/rpc.gssd.debug
sh-3.1# /usr/lib/debug/usr/sbin/rpc.gssd.debug -f
sh: /usr/lib/debug/usr/sbin/rpc.gssd.debug: Permission denied
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2007-01-29 23:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-27 15:20 question about fh_copy Ming Zhang
2007-01-28 23:01 ` J. Bruce Fields
2007-01-29 0:36 ` Ming Zhang
2007-01-29 1:04 ` J. Bruce Fields
2007-01-29 14:10 ` Ming Zhang
2007-01-29 20:35 ` rpc.gssd segfault on FC5 client Jim Davis
2007-01-29 22:02 ` Kevin Coffman
2007-01-29 22:06 ` Jim Davis
2007-01-29 22:44 ` Kevin Coffman
2007-01-29 22:49 ` Jim Davis
2007-01-29 23:18 ` Kevin Coffman
2007-01-29 23:34 ` Jim Davis [this message]
2007-01-30 0:02 ` Kevin Coffman
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=45BE848B.2030907@CS.Arizona.EDU \
--to=jdavis@cs.arizona.edu \
--cc=kwc@citi.umich.edu \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.