Leon Kirsch <[EMAIL PROTECTED]> writes: |> Intentionally I didn't change the line of code in |> scalar.cc, to see if this would trigger a segfault. |> |> Nothing the like happened. It compiled and runs without |> crashing under S.u.S.E-6.1 and S.u.S.E-6.2. So what? That does not prove anything. Welcome to the world of undefined behaviour. Andreas. -- Andreas Schwab "And now for something SuSE Labs completely different." [EMAIL PROTECTED] SuSE GmbH, Schanzäckerstr. 10, D-90443 Nürnberg
- Re: SIGSEV in lilypond 1.2.9 under SuSE 6.... Ekkehard Ellmann
- Re: SIGSEV in lilypond 1.2.9 under SuSE 6.2 Howard E. Motteler
- Re: SIGSEV in lilypond 1.2.9 under SuSE 6.2 Han-Wen Nienhuys
- Re: SIGSEV in lilypond 1.2.9 under SuSE 6.2 Howard E. Motteler
- Re: SIGSEV in lilypond 1.2.9 under SuSE 6.... Jan Nieuwenhuizen
- Re: SIGSEV in lilypond 1.2.9 under SuS... Howard E. Motteler
- Re: SIGSEV in lilypond 1.2.9 unde... Karl Eichwalder
- Re: SIGSEV in lilypond 1.2.9 ... Jan Nieuwenhuizen
- Re: SIGSEV in lilypond 1.2.9 under SuSE 6.2 Andreas Schwab
- Re: SIGSEV in lilypond 1.2.9 under SuSE 6.2 Leon Kirsch
- Re: SIGSEV in lilypond 1.2.9 under SuSE 6.2 Andreas Schwab
- Re: SIGSEV in lilypond 1.2.9 under SuSE 6.2 Karl Eichwalder