On 6/30/09 12:16 PM, "Patrick McCarty" wrote:
> On Tue, Jun 30, 2009 at 11:53:34AM -0600, Carl D. Sorensen wrote:
>>
>> On 6/30/09 11:02 AM, "Patrick McCarty" wrote:
>>
>> However, on a hunch I decided to look at the .gdbinit file. I had been
>> using the .gdbinit file from the CG. When I
On Tue, Jun 30, 2009 at 11:53:34AM -0600, Carl D. Sorensen wrote:
>
> On 6/30/09 11:02 AM, "Patrick McCarty" wrote:
> >
> > When I compile LilyPond with the intent of debugging it, I use
> >
> > ./configure --disable-optimising
> >
> > instead. Did you try that?
>
> I had not. I also hadn't
On 6/30/09 11:02 AM, "Patrick McCarty" wrote:
> On Tue, Jun 30, 2009 at 08:40:05AM -0600, Carl D. Sorensen wrote:
>> I'm trying to get the CG instructions for using gdb up-to-date. And I'm
>> trying to debug a problem with the new autobeam stuff I'm working on.
>>
>> So I checked out a fresh
On Tue, Jun 30, 2009 at 08:40:05AM -0600, Carl D. Sorensen wrote:
> I'm trying to get the CG instructions for using gdb up-to-date. And I'm
> trying to debug a problem with the new autobeam stuff I'm working on.
>
> So I checked out a fresh master.
>
> Then I did
>
> ./configure --enable-debugg
> Any thoughts on how to debug this segmentation fault in gdb?
You might try to run valgrind on lilypond, ignoring the zillions of
warnings regarding Scheme (or use a valgrind suppress file -- a few
years ago Han-Wen has posted something): This should give you the `hot
spot' which causes the segf
I'm trying to get the CG instructions for using gdb up-to-date. And I'm
trying to debug a problem with the new autobeam stuff I'm working on.
So I checked out a fresh master.
Then I did
./configure --enable-debugging
make
gdb lilypond
GNU gdb 6.3.50-20050815 (Apple version gdb-768) (Tue Oct
