timidity: segfault with --force-program for a nonexistent patch

[asari]

When executing timidity from a web application (written in Python), timidity crashes with segmentation fault.

In a minimal environment I haven't reproduced the problem yet for now, but could obtain the core dump in our production environment (attached). I'll continue investigating the webapp, but let me post the backtrace here.

asari$ uname -a; lsb_release -a
Linux m20010 2.6.38-8-generic #42-Ubuntu SMP Mon Apr 11 03:31:50 UTC 2011 i686 i686 i386 GNU/Linux
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 11.04
Release: 11.04
Codename: natty

[asari (asari-users)]

Here is the Apache error log which our webapp wrote (attached).

[asari (asari-users)]

I could reproduce the problem with --force-program=.. option and attached .midi file (created by lilypond).

$ timidity 94-s3JM_div1.midi -Ow --force-program=12 -o /tmp/94-s3JM_div1.wav
Playing 94-s3JM_div1.midi
MIDI file: 94-s3JM_div1.midi
Format: 1 Tracks: 5 Divisions: 384
Sequence: control track
Text: creator:
Text: GNU LilyPond 2.12.3
Track name: \new
Track name:
Track name: upper
Track name: lower
Segmentation fault

In my environment, timidity seems to fail with segmentation fault if any of following number were given:

3,10,11,12,17,18,20,22,31,39,41,43,49,50,51,52,54,55,62,63,77,78,81,82,83,85,86,87,89,90,91,92,93,96,97,99,100,103,105,106,107,108,109,110,111,112,113,116,117,118,119,121,123,124,126,127

[asari (asari-users)]

> In my environment, timidity seems to fail with segmentation fault if any of following number were given:
>
> 3,10,11,12,17,18,20,22,31,39,41,43,49,50,51,52,54,55,62,63,77,78,81,82,83,85,86,87,89,90,91,92,93,96,97,99,100,103,105,106,107,108,109,110,111,112,113,116,117,118,119,121,123,124,126,127

It should be "if any of following number were given _to the argument of --force-program ." Sorry.

[asari (asari-users)]

Above list fits with the tones not exist in /etc/timidity/freepats.cfg.
I used timidity++ with default freepats which came with it.

Probably the title of this bug should be "Segmentation fault on executing with --force-program <not yet configured tone>".

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.