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 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", atype=1, aparent=-137545022,
> avolid=0x20005be7,
> atrans=0xf7cd3e6c) at volprocs.c:376
> #2 0x0001f748 in AFSVolExecuteRequest (z_call=0x176d00) at volint.ss.c:24
> #3 0x00047fbc in rxi_ServerProc (threadID=1535232, newcall=<value
> optimized out>,
> socketp=0xf7cd3f5c) at rx.c:1413
> #4 0x00040120 in rx_ServerProc () at rx_lwp.c:371
> #5 0x0004f5d4 in Create_Process_Part2 ()
> #6 0x0004fce8 in savecontext ()
> #7 0xfcfdff0b in ?? ()
> #8 0xfcfdff0b in ?? ()
> Previous frame identical to this frame (corrupt stack?)
> (gdb)
>
>
> --
> PGP/GPG: 5C9F F366 C9CF 2145 E770 B1B8 EFB1 462D A146 C380
>
> _______________________________________________
> OpenAFS-info mailing list
> [email protected]
> https://lists.openafs.org/mailman/listinfo/openafs-info
>
