talloc & threads in rlm_eap

[Phil Mayers]

On 23/06/2014 20:31, Arran Cudbard-Bell wrote:

> The original cbuff code should work now and provide you with the alloc and free BTs.

Sorry I still get "No backtrace"

#9  0x00007f0283082134 in fr_verify_vp (file=0x7f02830a6510 
"src/lib/cursor.c", line=45, vp=0x7f0210005640) at src/lib/debug.c:813
No locals.
#10 0x00007f028308093f in _fr_cursor_init (cursor=0x7fff3a10e310, 
node=0x7fff3a10e2f0) at src/lib/cursor.c:45
---Type <return> to continue, or q <return> to quit---q
Quit
(gdb) call backtrace_print(&vp_bt, 0x7f0210005640)
Backtrace attached to VALUE_PAIR 0x7f02040233d0
Backtrace attached to VALUE_PAIR 0x7f0204038cb0
Backtrace attached to VALUE_PAIR 0x7f020409c720
Backtrace attached to VALUE_PAIR 0x7f0200005c30
Backtrace attached to VALUE_PAIR 0x7f02100ff720
Backtrace attached to VALUE_PAIR 0x7f0224031c90
Backtrace attached to VALUE_PAIR 0x119ca90
Backtrace attached to VALUE_PAIR 0x7f021c015390
Backtrace attached to VALUE_PAIR 0x7f0230004f50
Backtrace attached to VALUE_PAIR 0x7f0204038cb0
Backtrace attached to VALUE_PAIR 0x119ccb0
Backtrace attached to VALUE_PAIR 0x7f02040baff0
Backtrace attached to VALUE_PAIR 0x7f0200005c30
Backtrace attached to VALUE_PAIR 0x7f02380d3a70
Backtrace attached to VALUE_PAIR 0x7f0230004f50
Backtrace attached to VALUE_PAIR 0x7f02380d4650
No backtrace available for 0x7f0210005640

...though by the look of it, the process is still proceeding when 
backtrace_print() is called, no idea if that has something to do with it.