Re: Reporting bugs of macosx binary builds
Grzegorz Adam Hankiewicz wrote: I've started working with lyx 1.6.2 under macosx, and sometimes the application crashes randomly. I've been unable to reproduce these crashes, but when I open macosx' bug report window there is a stack trace with the C++ code calls that happened before the crash. I was wondering if this information is useful to somebody, since I read on the lyx' website that unreproducible bugs are ignored. You could post the backtrace, but if you're not using a debug-enabled build, it might not mean much. Bugs we can't reproduce aren't so much ignored as, well, hard to work on. I.e., impossible to work on. Richard
Re: Reporting bugs of macosx binary builds
Grzegorz Adam Hankiewicz wrote: I've started working with lyx 1.6.2 under macosx, and sometimes the application crashes randomly. I've been unable to reproduce these crashes, but when I open macosx' bug report window there is a stack trace with the C++ code calls that happened before the crash. I was wondering if this information is useful to somebody, since I read on the lyx' website that unreproducible bugs are ignored. You could post the backtrace, but if you're not using a debug-enabled build, it might not mean much. Bugs we can't reproduce aren't so much ignored as, well, hard to work on. I.e., impossible to work on. Richard
Re: Reporting bugs of macosx binary builds
Grzegorz Adam Hankiewicz wrote: I've started working with lyx 1.6.2 under macosx, and sometimes the application crashes randomly. I've been unable to reproduce these crashes, but when I open macosx' bug report window there is a stack trace with the C++ code calls that happened before the crash. I was wondering if this information is useful to somebody, since I read on the lyx' website that unreproducible bugs are ignored. You could post the backtrace, but if you're not using a debug-enabled build, it might not mean much. Bugs we can't reproduce aren't so much ignored as, well, hard to work on. I.e., impossible to work on. Richard
