Help with OS X issue please

[James Westby]

On Mon, 2008-03-03 at 11:12 -0600, Brian de Alwis wrote:
> On 2-Mar-2008, at 5:59 PM, James Westby wrote:
> > In particular I would like a backtrace from when bzr is
> > hanging, however I don't know how to generate a SIGQUIT
> > on OS X to get this.
> 
> 
> By default, MacOSX sets the core rlimit to 0 and so won't produce  
> cores.  The core files seem to be put in /cores/core.<pid> by  
> default.  This location can be changed by the sysctl kern.corefile.
> 
> ^\ should produce a SIGQUIT (it does on my testing).  But a SIGQUIT  
> may take some time writing a core file and a crash report to ~/Library/ 
> Logs/CrashReporter/.  Doing ^\ on cat(1) takes roughly 5 seconds on my  
> simple tests and produces a 200MB core file (!).

Hi,

bzr installs its own signal handler for SIGQUIT that drops you in to
a pdb session, allowing you to query variables and obtain a backtrace
that way.

To everyone else, we have managed to track down what was causing the
issue, and we are looking to see if we can avoid it at all. Although a
quick search for this issue shows that it breaks a lot of things, so
it's probably not to important to add a workaround.

Thanks,

James