Package: subversion
Version: 1.8.10-3
Followup-For: Bug #736879
Hi,
unfortunately I can still confirm this issue in current Jessie. Here is
a backtrace:
(gdb) bt
#0 0x00007fffefdce0a6 in kwallet_password_set (done=0x7fffffffd714,
creds=<optimized out>,
realmstring=0x7ffff7e29440 "<https://svn.domain:443> DNS Subversion
Repository (ADS Password)", username=0x7fffe9af9478 "USERNAME",
password=0x7fffe9af9668 "PASSWORD", parameters=0x7ffff7e30028,
non_interactive=0, pool=0x7ffff7e2e028)
at
/build/subversion-m07Dw3/subversion-1.8.10/subversion/libsvn_auth_kwallet/kwallet.cpp:317
#1 0x00007ffff7055622 in svn_auth__simple_creds_cache_set
(saved=0x7fffffffd714, credentials=0x7fffe9af9230,
provider_baton=0x7fffe9af9748,
parameters=0x7ffff7e30028, realmstring=0x13 <error: Cannot access memory at
address 0x13>, password_set=0x7fffefdced64, passtype=0x7fffefdced48 "kwallet",
pool=0x7ffff7e2e028) at
/build/subversion-m07Dw3/subversion-1.8.10/subversion/libsvn_subr/simple_providers.c:458
#2 0x00007fffefdcda5a in kwallet_simple_save_creds (saved=<optimized out>,
credentials=<optimized out>, provider_baton=<optimized out>,
parameters=<optimized out>,
realmstring=<optimized out>, pool=<optimized out>) at
/build/subversion-m07Dw3/subversion-1.8.10/subversion/libsvn_auth_kwallet/kwallet.cpp:372
#3 0x00007ffff702cdf5 in svn_auth_save_credentials (state=0x7ffff7e29410,
pool=0x7ffff7e2e028)
at
/build/subversion-m07Dw3/subversion-1.8.10/subversion/libsvn_subr/auth.c:379
#4 0x00007ffff5712fbb in handle_response (scratch_pool=<optimized out>,
serf_status=<optimized out>, handler=<optimized out>, response=<optimized out>,
request=<optimized out>) at
/build/subversion-m07Dw3/subversion-1.8.10/subversion/libsvn_ra_serf/util.c:2116
#5 handle_response_cb (request=0x7ffff7e06038, response=0x7ffff7e1b0b8,
baton=0x7ffff7fd5488, scratch_pool=0x7fffe9afa028)
at
/build/subversion-m07Dw3/subversion-1.8.10/subversion/libsvn_ra_serf/util.c:2275
#6 0x00007ffff37d043e in serf.process_connection () from
/usr/lib/x86_64-linux-gnu/libserf-1.so.1
#7 0x00007ffff37cecce in serf_event_trigger () from
/usr/lib/x86_64-linux-gnu/libserf-1.so.1
#8 0x00007ffff37cedec in serf_context_run () from
/usr/lib/x86_64-linux-gnu/libserf-1.so.1
#9 0x00007ffff571182a in svn_ra_serf__context_run_wait
(done=done@entry=0x7ffff7fd54a4, sess=0x7ffff7fd5100,
scratch_pool=scratch_pool@entry=0x7ffff7fd5028)
at
/build/subversion-m07Dw3/subversion-1.8.10/subversion/libsvn_ra_serf/util.c:917
#10 0x00007ffff57129b4 in svn_ra_serf__context_run_one (handler=0x7ffff7fd5488,
scratch_pool=scratch_pool@entry=0x7ffff7fd5028)
at
/build/subversion-m07Dw3/subversion-1.8.10/subversion/libsvn_ra_serf/util.c:982
#11 0x00007ffff5705950 in svn_ra_serf__exchange_capabilities
(serf_sess=serf_sess@entry=0x7ffff7fd5100,
corrected_url=corrected_url@entry=0x7fffffffdbd8,
pool=pool@entry=0x7ffff7fd5028) at
/build/subversion-m07Dw3/subversion-1.8.10/subversion/libsvn_ra_serf/options.c:491
#12 0x00007ffff570b367 in svn_ra_serf__open (session=<optimized out>,
corrected_url=0x7fffffffdbd8, session_URL=<optimized out>,
callbacks=0x7ffff7fe2bb0,
callback_baton=<optimized out>, config=<optimized out>,
pool=0x7ffff7fd5028) at
/build/subversion-m07Dw3/subversion-1.8.10/subversion/libsvn_ra_serf/serf.c:541
This is reproducible. Basically the only way to cleanly checkout
repositories is to ignore the segfault, change into the working
directory, run "svn cleanup" followed by an "svn update". In some cases
svn asks for the password again, in some cases it was successful in
storing the password before the crash happened and the update runs
without further interaction.
Bernhard
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
