Nathan Fiedler <nfiedler@bluemarsh.com> writes:
> Invoking 'svn --version' causes a segmentation fault. I'm a gdb newbie,
> so this is all I knew how to do:
>
> (gdb) run --version
> Starting program: /usr/local/bin/svn --version
> [New Thread 1024 (LWP 25333)]
>
> Program received signal SIGSEGV, Segmentation fault.
> [Switching to Thread 1024 (LWP 25333)]
> 0x4021a254 in apr_getopt_long (os=0x8059ea0, opts=0x8050fa0,
> optch=0xbffff76c,
> optarg=0xbffff768) at getopt.c:240
> 240 getopt.c: No such file or directory.
> in getopt.c
> (gdb) bt
> #0 0x4021a254 in apr_getopt_long (os=0x8059ea0, opts=0x8050fa0,
> optch=0xbffff76c, optarg=0xbffff768) at getopt.c:240
> #1 0x0804c44d in main (argc=2, argv=0xbffff7f4)
> at subversion/clients/cmdline/main.c:807
> #2 0x402c1306 in __libc_start_main (main=0x804c360 <main>, argc=2,
> ubp_av=0xbffff7f4, init=0x8049c70 <_init>, fini=0x8050910 <_fini>,
> rtld_fini=0x4000d2dc <_dl_fini>, stack_end=0xbffff7ec)
> at ../sysdeps/generic/libc-start.c:129
We've seen this happen when APR is out-of-date.
Now, I know that you checked out the latest httpd-2.0 from CVS, and
that you told subversion to use the APR included there. But maybe
that's not working for some reason. Maybe your svn is finding an
older installed APR.
In particular, a couple months back I added a final "description"
field to apr/include/apr_getopt.h:apr_getopt_option_t. If people
forgot to update APR, they'd see segfaults like this.
As an experiment: can you try checking out the latest APR and
APR-UTIL directly into your subversion tree, and then recompile
without any --with-apr config options? See if that makes a
difference.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Apr 9 21:31:02 2002