Bug#732342: Stack Trace

2014-01-15 Thread Andrew Bartlett
On Tue, 2014-01-07 at 16:58 -0800, Steve Langasek wrote: > On Wed, Jan 08, 2014 at 01:54:32PM +1300, Andrew Bartlett wrote: > > > > > Reading symbols from /usr/lib/x86_64-linux-gnu/libhdb.so.9...Reading > > > > symbols from > > > > /usr/lib/debug/usr/lib/x86_64-linux-gnu/libhdb.so.9.2.0...done. >

Bug#732342: Stack Trace

2014-01-09 Thread Jeff Clark
No problem. Will send it over in a few hours. On Thu, Jan 9, 2014 at 5:14 PM, Andrew Bartlett wrote: > On Fri, 2014-01-10 at 12:12 +1300, Andrew Bartlett wrote: >> On Thu, 2014-01-09 at 16:04 -0600, Jeff Clark wrote: >> > Samba needs the hdb plugin updated to support hdb version 8. >> > >> > >>

Bug#732342: Stack Trace

2014-01-09 Thread Andrew Bartlett
On Fri, 2014-01-10 at 12:12 +1300, Andrew Bartlett wrote: > On Thu, 2014-01-09 at 16:04 -0600, Jeff Clark wrote: > > Samba needs the hdb plugin updated to support hdb version 8. > > > > > > > > Heimdal needs the hdb callback function patched because even when the > > plugin is registered properl

Bug#732342: Stack Trace

2014-01-09 Thread Andrew Bartlett
On Thu, 2014-01-09 at 16:04 -0600, Jeff Clark wrote: > Samba needs the hdb plugin updated to support hdb version 8. > > > > Heimdal needs the hdb callback function patched because even when the > plugin is registered properly, it segfaults because the pointer is > never set properly in _krb5_plu

Bug#732342: Stack Trace

2014-01-09 Thread Jeff Clark
Samba needs the hdb plugin updated to support hdb version 8. Heimdal needs the hdb callback function patched because even when the plugin is registered properly, it segfaults because the pointer is never set properly in _krb5_plugin_run_f. Looks like the plugin code was recently updated but never

Bug#732342: Stack Trace

2014-01-09 Thread Pat Suwalski
On 14-01-07 08:29 PM, Andrew Bartlett wrote: >What are the relevant values of "in-sync-ness" for heimdal? I would prefer it was exactly the version we have in-tree, but that's now quite old. So, it would seem that the present solution is that samba should be updating the heimdal snapshot, doc

Bug#732342: [Pkg-samba-maint] Bug#732342: Stack Trace

2014-01-07 Thread Andrew Bartlett
On Wed, 2014-01-08 at 14:29 +1300, Andrew Bartlett wrote: > On Tue, 2014-01-07 at 16:58 -0800, Steve Langasek wrote: > > On Wed, Jan 08, 2014 at 01:54:32PM +1300, Andrew Bartlett wrote: > > > > > > > Reading symbols from /usr/lib/x86_64-linux-gnu/libhdb.so.9...Reading > > > > > symbols from > > >

Bug#732342: Stack Trace

2014-01-07 Thread Andrew Bartlett
On Tue, 2014-01-07 at 16:58 -0800, Steve Langasek wrote: > On Wed, Jan 08, 2014 at 01:54:32PM +1300, Andrew Bartlett wrote: > > > > > Reading symbols from /usr/lib/x86_64-linux-gnu/libhdb.so.9...Reading > > > > symbols from > > > > /usr/lib/debug/usr/lib/x86_64-linux-gnu/libhdb.so.9.2.0...done. >

Bug#732342: Stack Trace

2014-01-07 Thread Steve Langasek
On Wed, Jan 08, 2014 at 01:54:32PM +1300, Andrew Bartlett wrote: > > > Reading symbols from /usr/lib/x86_64-linux-gnu/libhdb.so.9...Reading > > > symbols from > > > /usr/lib/debug/usr/lib/x86_64-linux-gnu/libhdb.so.9.2.0...done. > > > done. > > > Loaded symbols for /usr/lib/x86_64-linux-gnu/libhdb

Bug#732342: Stack Trace

2014-01-07 Thread Andrew Bartlett
On Tue, 2014-01-07 at 15:11 -0800, Steve Langasek wrote: > On Tue, Jan 07, 2014 at 05:48:16PM -0500, Pat Suwalski wrote: > > It is surprisingly difficult to get a stack trace, even with > > samba-dbg and heimdal-dbg installed: > > > #0 0x in ?? () > > #1 0x7f58b4821ff5 in ??

Bug#732342: Stack Trace

2014-01-07 Thread Steve Langasek
On Tue, Jan 07, 2014 at 05:48:16PM -0500, Pat Suwalski wrote: > It is surprisingly difficult to get a stack trace, even with > samba-dbg and heimdal-dbg installed: > #0 0x in ?? () > #1 0x7f58b4821ff5 in ?? () > #2 0x7fff2c599618 in ?? () > #3 0x7f58ba31f260 in ?? (

Bug#732342: Stack Trace

2014-01-07 Thread Pat Suwalski
It is surprisingly difficult to get a stack trace, even with samba-dbg and heimdal-dbg installed: #0 0x in ?? () #1 0x7f58b4821ff5 in ?? () #2 0x7fff2c599618 in ?? () #3 0x7f58ba31f260 in ?? () #4 0x7f58ba8e57e0 in ?? () #5 0x7f58ba2c6280 in ?? () #6 0x