[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
signal 11 strack trace(?)
From: |
Han-Wen Nienhuys |
Subject: |
signal 11 strack trace(?) |
Date: |
Tue, 17 Feb 2004 23:47:00 +0100 |
address@hidden writes:
> I don't know if I did it right or not but I fired up gdb, and it seems I
> managed to run LilyPond in it on 'wrong.ly' and this is what it spat
> out:
>
> Starting program: /usr/local/bin/lilypond-bin wrong.ly
> (no debugging symbols found)...(no debugging symbols found)...
> (no debugging symbols found)...(no debugging symbols found)...[New
> Thread 1075823520 (LWP 3788)]
>
> (no debugging symbols found)...(no debugging symbols found)...
> (no debugging symbols found)...(no debugging symbols found)...
> (no debugging symbols found)...(no debugging symbols found)...
> (no debugging symbols found)...(no debugging symbols found)...
> Now processing: `wrong.ly'
> Parsing...Interpreting music...
> Program received signal SIGSEGV, Segmentation fault.
> [Switching to Thread 1075823520 (LWP 3788)]
> 0x0811e743 in strcpy ()
> (gdb)
>
> If there is some other procedure I should perform I'll be glad to try.
The procedure is:
* make sure that lily is compiled with "-g" in the g++ command
line. (add -g to CXXFLAGS in config.make if not sure)
* do
gdb lily/out/lilypond-bin
* do
r wrong.ly
(crash)
* type "bt"
--
Han-Wen Nienhuys | address@hidden | http://www.xs4all.nl/~hanwen