28 Oct
2005
28 Oct
'05
9:51 a.m.
On Thursday 27 October 2005 14:33, Lars Luthman wrote:
On Wed, 2005-10-26 at 17:00 +0200, Marcos Guglielmetti
wrote:
Now it did not produced segmentation fault (but it didn't work too), details
are into "prueba" file
--
Marcos
fecha: vie oct 28 07:25:02 CEST 2005
Ok, I tried with:
/usr/lib/dssi/sineshaper/sineshaper_gtk
osc.udp://Musix_GNU+Linux:17067/dssi/sineshaper/ll-sineshaper/inst00
sineshaper.so sineshaper Testing
Violación de segmento
Translated:
"Segmentation Fault"
Oh, no... :(
No, this is good - segmentation faults are often a lot easier to debug
than a program that doesn't crash but still doesn't do what it's
supposed to do.
A backtrace would be very useful. You can get one by running
'gdb /usr/lib/dssi/sineshaper/sineshaper_gtk core.*' and then typing 'bt
full' (where core.* is the name of the dumped core file which should
have been generated when you got the segmentation fault, if you didn't
get a core file you can try running the command 'ulimit -c unlimited' in
the shell and then run the GUI again, with the same arguments as last
time).