"Derrick Brashear" <[EMAIL PROTECTED]> writes:
> in my source that's
> vnode->dataVersion = 1;
> (on line 257)
>
> What's it in yours?
Same.
- a
___
OpenAFS-info mailing list
OpenAFS-info@openafs.org
https://lists.openafs.org/mailman/listinfo/op
in my source that's
vnode->dataVersion = 1;
(on line 257)
What's it in yours?
And really, don't cc openafs-bugs in mail to the list. Every reply doesn't
need its own ticket.
On 11/3/07, Adam Megacz <[EMAIL PROTECTED]> wrote:
>
>
> Jeffrey Altman <[EMAIL PROTECTED]> writes:
> > Stack trace fr
Adam Megacz <[EMAIL PROTECTED]> writes:
> Could anybody tell me where volserver leaves its core dumps? (the
> answer is not /var/lib/openafs/cores/)
/var/log/openafs.
The cores directory is a misunderstanding in the Debian package and is no
longer created by the latest version. It wasn't used b
On Sat, 3 Nov 2007, Adam Megacz wrote:
"Christopher D. Clausen" <[EMAIL PROTECTED]> writes:
Could anybody tell me where volserver leaves its core dumps? (the
answer is not /var/lib/openafs/cores/)
Probably depends on the platform. On sun4x_510, I think cores ended up
in /usr/afs/logs
Tha
Jeffrey Altman <[EMAIL PROTECTED]> writes:
> Stack trace from core?
Got it. Recompiling with gcc-3.4 (rather than debian's 4.1.2) made
the problem go away. Go figure.
- a
) at volprocs.c:257
#1 0x00016c34 in SAFSVolCreateVolume (acid=0xf7cd3c4c, apart=1534752,
aname=0x176a48 "krunk899
"Christopher D. Clausen" <[EMAIL PROTECTED]> writes:
>> Could anybody tell me where volserver leaves its core dumps? (the
>> answer is not /var/lib/openafs/cores/)
> Probably depends on the platform. On sun4x_510, I think cores ended up
> in /usr/afs/logs
Thanks, but no luck. This is linux-sp
Adam Megacz <[EMAIL PROTECTED]> wrote:
> Could anybody tell me where volserver leaves its core dumps? (the
> answer is not /var/lib/openafs/cores/)
>
> I have to honestly admit I've never debugged a program via core dumps
> before. Always used printf() or [last resort] gdb.
>
> Unfortunately in my
Hello,
Could anybody tell me where volserver leaves its core dumps? (the
answer is not /var/lib/openafs/cores/)
I have to honestly admit I've never debugged a program via core dumps
before. Always used printf() or [last resort] gdb.
Unfortunately in my current situation, attaching gdb to any o
