View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0001185 | ardour | bugs | public | 2006-02-07 05:32 | 2008-11-20 23:57 |
| Reporter | indigo | Assigned To | paul | ||
| Priority | normal | Severity | crash | Reproducibility | always |
| Status | closed | Resolution | fixed | ||
| Summary | 0001185: (actually 0.99.1) segfault while playing with midi control | ||||
| Description | I can get ardour to segfault thus: - create a new session - right click in the region to the left of the main canvas to add a new track. First do one stereo, then 2 mono. - hit the 'editor mixer' button at the top left - for each track, from top to bottom, ctrl-click to assign a midi control. Assign separate midi controls for each. - open the options window from the menu at the top - in the midi tab, enable all the midi control options (one is on by default; enable mmc control, send mmc, and send feedback) - in the editor mixer, middle-click the number above the fader for each channel to set it to 0 dB - move the faders on my midi device up and down for a few seconds. - segfault. | ||||
| Additional Information | Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 46912539054000 (LWP 14548)] 0x00002aaaab225b83 in gtk_widget_hide () from /usr/lib/libgtk-1.2.so.0 (gdb) thread apply all bt Cannot find new threads: generic error (gdb) bt #0 0x00002aaaab225b83 in gtk_widget_hide () from /usr/lib/libgtk-1.2.so.0 Error accessing memory address 0x7fffffb19728: No such process. (gdb) | ||||
| Tags | No tags attached. | ||||
|
|
If I start jack without realtime, and with -t10000, then behaivour is the same but I can get this traceback: Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 46912539054000 (LWP 14601)] 0x00002aaaab225b6f in gtk_widget_hide () from /usr/lib/libgtk-1.2.so.0 (gdb) thread apply all bt Thread 7 (Thread 1124096352 (LWP 14609)): #0 0x00002aaaad01b5d2 in poll () from /lib/libc.so.6 0000001 0x00000000008651cb in ARDOUR::Session::feedback_thread_work (this=0x13a9ff0) at libs/ardour/session_feedback.cc:137 #2 0x0000000000865579 in ARDOUR::Session::_feedback_thread_work (arg=0x13a9ff0) at libs/ardour/session_feedback.cc:112 #3 0x00002aaaac9020fa in start_thread () from /lib/libpthread.so.0 0000004 0x00002aaaad024383 in clone () from /lib/libc.so.6 0000005 0x0000000000000000 in ?? () #6 0x0000000000000000 in ?? () ... 0000209 0x0000000000000000 in ?? () 0000210 0x0000000000000000 in ?? () 0000211 0x0000000000000000 in ?? () 0000212 0x0000000000000000 in ?? () 0000213 0x00002aaaad18e0e0 in __check_rhosts_file () from /lib/libc.so.6 0000214 0x0000000043005dc0 in ?? () 0000215 0x000000000000000b in ?? () Previous frame inner to this frame (corrupt stack?) #0 0x00002aaaab225b6f in gtk_widget_hide () from /usr/lib/libgtk-1.2.so.0 |
|
|
Is this still a problem? |
|
|
in the unlikely event that this is still an issue (i think this is fixed even in 0.99.3), the code in ardour2 for this is totally different and i'd rather see a new bug. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2006-02-07 05:32 | indigo | New Issue | |
| 2006-02-07 05:38 | indigo | Note Added: 0002447 | |
| 2007-02-16 22:53 | taybin | Note Added: 0003312 | |
| 2007-02-26 16:17 | paul | Status | new => resolved |
| 2007-02-26 16:17 | paul | Resolution | open => fixed |
| 2007-02-26 16:17 | paul | Assigned To | => paul |
| 2007-02-26 16:17 | paul | Note Added: 0003399 | |
| 2008-11-20 23:57 | seablade | Status | resolved => closed |
