Re: Segfault 2.15.23 Span_bar_stub_engraver

2012-01-05 Thread David Kastrup
"m...@apollinemike.com" writes: > On Jan 5, 2012, at 11:24 AM, David Kastrup wrote: > >> m...@apollinemike.com writes: >> >>> On Jan 5, 2012, at 7:51 AM, David Kastrup wrote: >>> Grob::get_vertical_axis_group is not protected against the case where g has an axis group interface but no

Re: Segfault 2.15.23 Span_bar_stub_engraver

2012-01-05 Thread m...@apollinemike.com
On Jan 5, 2012, at 11:24 AM, David Kastrup wrote: > m...@apollinemike.com writes: > >> On Jan 5, 2012, at 7:51 AM, David Kastrup wrote: >> >>> Grob::get_vertical_axis_group is not protected against the case where g >>> has an axis group interface but no Y_AXIs parent. >> >> I thought it was.

Re: Segfault 2.15.23 Span_bar_stub_engraver

2012-01-05 Thread David Kastrup
m...@apollinemike.com writes: > On Jan 5, 2012, at 7:51 AM, David Kastrup wrote: > >> Grob::get_vertical_axis_group is not protected against the case where g >> has an axis group interface but no Y_AXIs parent. > > I thought it was. If g has no Y_AXIS parent, then when > get_vertical_axis_group (

Re: Segfault 2.15.23 Span_bar_stub_engraver

2012-01-05 Thread mike
On Jan 5, 2012, at 7:51 AM, David Kastrup wrote: > Grob::get_vertical_axis_group is not protected against the case where g > has an axis group interface but no Y_AXIs parent. I thought it was. If g has no Y_AXIS parent, then when get_vertical_axis_group (g->get_parent (Y_AXIS)); is called, the

Re: Segfault 2.15.23 Span_bar_stub_engraver

2012-01-04 Thread David Kastrup
Jay Anderson writes: > On Wed, Jan 4, 2012 at 1:41 AM, David Kastrup wrote: >> Can you use git bisect for identifying the commit where things go wrong >> for you? > > Git bisect results: > 20670d51f8d97fd390210dd239b3b2427f071e7c is the first bad commit > commit 20670d51f8d97fd390210dd239b3b2427

Re: Segfault 2.15.23 Span_bar_stub_engraver

2012-01-04 Thread Jay Anderson
On Wed, Jan 4, 2012 at 1:41 AM, David Kastrup wrote: > Can you use git bisect for identifying the commit where things go wrong > for you? Git bisect results: 20670d51f8d97fd390210dd239b3b2427f071e7c is the first bad commit commit 20670d51f8d97fd390210dd239b3b2427f071e7c Author: Mike Solomon Date

Re: Segfault 2.15.23 Span_bar_stub_engraver

2012-01-04 Thread David Kastrup
Jay Anderson writes: > On Tue, Jan 3, 2012 at 1:12 AM, m...@apollinemike.com > wrote: >> On Jan 3, 2012, at 9:02 AM, David Kastrup wrote: >>> If he hadn't rerun configure since before version 2.15.21, I think that >>> the compilation would likely have failed for other reasons.  The problem >>> r

Re: Segfault 2.15.23 Span_bar_stub_engraver

2012-01-03 Thread Jay Anderson
On Tue, Jan 3, 2012 at 1:12 AM, m...@apollinemike.com wrote: > On Jan 3, 2012, at 9:02 AM, David Kastrup wrote: >> If he hadn't rerun configure since before version 2.15.21, I think that >> the compilation would likely have failed for other reasons.  The problem >> report is for 2.15.23.  It may b

Re: Segfault 2.15.23 Span_bar_stub_engraver

2012-01-03 Thread m...@apollinemike.com
On Jan 3, 2012, at 9:02 AM, David Kastrup wrote: > Keith OHara writes: > >> Jay Anderson gmail.com> writes: >> >>> On Mon, Jan 2, 2012 at 6:41 PM, Keith OHara oco.net> >>> wrote: I can't produce the segfault, either. >>> >>> Strange I can consistently reproduce it (just pulled t

Re: Segfault 2.15.23 Span_bar_stub_engraver

2012-01-03 Thread David Kastrup
Keith OHara writes: > Jay Anderson gmail.com> writes: > >> On Mon, Jan 2, 2012 at 6:41 PM, Keith OHara oco.net> wrote: >> > >> > I can't produce the segfault, either. >> >> Strange I can consistently reproduce it (just pulled the latest and >> recompiled): Ubuntu 11.10, gcc 4.6.1. > > If you h

Re: Segfault 2.15.23 Span_bar_stub_engraver

2012-01-02 Thread Keith OHara
Jay Anderson gmail.com> writes: > On Mon, Jan 2, 2012 at 6:41 PM, Keith OHara oco.net> wrote: > > > > I can't produce the segfault, either. > > Strange I can consistently reproduce it (just pulled the latest and > recompiled): Ubuntu 11.10, gcc 4.6.1. If you have *only* seen it in compiles wit

Re: Segfault 2.15.23 Span_bar_stub_engraver

2012-01-02 Thread Jay Anderson
On Mon, Jan 2, 2012 at 6:41 PM, Keith OHara wrote: > mike apollinemike.com apollinemike.com> writes: >> Some meh news: I don't get a segfault ... >> Maybe someone else could give it a look? > > I can't produce the segfault, either. Strange I can consistently reproduce it (just pulled the latest

Re: Segfault 2.15.23 Span_bar_stub_engraver

2012-01-02 Thread Keith OHara
mike apollinemike.com apollinemike.com> writes: > Some meh news: I don't get a segfault ... > Maybe someone else could give it a look? I can't produce the segfault, either. Jay Anderson gmail.com> writes: > Removing the "Span_bar_stub_engraver" from my > PianoStaff fixes the segfault, but wha

Re: Segfault 2.15.23 Span_bar_stub_engraver

2012-01-01 Thread m...@apollinemike.com
On Jan 1, 2012, at 6:16 AM, Jay Anderson wrote: > On Sat, Dec 31, 2011 at 6:47 PM, m...@apollinemike.com > wrote: >> I wrote that engraver - could you send me the full file? I'll try to find >> the source of the bug... > > https://github.com/horndude77/open-scores/tree/master/ChevillardAllegro