Re: more on MT debugging

[<don...@is...>]

Pascal Bourguignon writes:

 > Specifically, any function in the CL package can be called
 > internally thru other mechanisms than provided to the user code:
 > the C code can call directly the C implementation of the CL
 > functions, without passing thru the CL API. Hence TRACE is allowed
 > NOT to work in those cases!
...

 > Instead, you can use gdb to break on those C functions.

I suppose that further, internal functions could be called from other 
functions, e.g., intern might call internal functions in hashtabl.d,
so it wouldn't be good enough to break only the external functions.

Is the current theory that only the file hashtabl.d has to be fixed 
for MT ?  Would it be worth while to try my test with a gdb break on 
every function in that file?

Does anyone have any other suggestions for trying to track down the
cause of a segfault once I can reproduce it?