View Issue Details

IDProjectCategoryView StatusLast Update
0000929ardourbugspublic2008-11-20 23:57
Reporterlukaz Assigned Topaul  
PrioritynormalSeveritycrashReproducibilityalways
Status closedResolutionfixed 
Summary0000929: midi assign cancel crash
Descriptionwhen I try to automate a mixerfader per Ctrl + middlebutton and ardour is not
via jack connected to my mpu401-midiport and I therefor cancel and try a
second time ardour will crash.

ardour will also crash if I try to automate once and cancel it and afterwards
turn a knob on my midicontroller.

I gues it will crash whenever I cancel the MIDI-automation (operate MIDI controll now) process and then come across with midi again.

on the console it prints out "Speicherzugriffsfehler". means someting like memoryaccessfailur

lukas
Additional Information2.6.11-gentoo
alsa 1.0.8
jack 0.99
ardour beta28 (is not choosable in mantis under Product-Version!)
TagsNo tags attached.

Activities

philicordas

2005-03-15 20:16

reporter   ~0002134

I see the same bug. Ardour beta28.
To reproduce...

Create a new session.
Create a mono track.
Add a plugin as an insert on that track.
Open the plugin's window.
Ctrl+middle click on a slider.
Close the 'Operate midi controller now' window without touching any midi controls.
Ctrl+middle click on *the same* slider.
Ardour segfaults.

Notes:
If you select a different slider the second time, there is no problem.

paul

2005-03-31 02:50

administrator   ~0002150

any chance of a gdb backtrace from either of you?

lukaz

2005-03-31 06:58

reporter   ~0002152

Sorry I can't do that but I'll ask my brother and if he's able I'll let you know.

philicordas

2005-04-03 18:55

reporter   ~0002164

Okay. This is with the cvs tarball...
Ardour gtk 0.583.0
libardour 0.883.0

I'm not quite sure how to use gdb, but this is what it displayed when doing the midi assign crash:

Loading session /mnt/hdd3/capture/swim/live using snapshot live
[New Thread 65541 (LWP 7739)]
[New Thread 81926 (LWP 7740)]
[New Thread 98311 (LWP 7741)]

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 16384 (LWP 7729)]
0x0846ce12 in gtk_widget_set_usize_to_display_given_text (w=0x41920050,
    text=0x41907024 "operate MIDI controller now", hpadding=25, vpadding=10)
    at libs/gtkmmext/gtkutils.c:37
37 gdk_string_extents (w->style->font,
Current language: auto; currently c

philicordas

2005-04-08 16:08

reporter   ~0002173

And again... this time with 'backtrace'... I think...

Loading session /gome/philicorda/ardoursongs/hello/hello using snapshot hello
[New Thread 65541 (LWP 9555)]
[New Thread 81926 (LWP 9556)]
[New Thread 98311 (LWP 9557)]

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 16384 (LWP 9545)]
0x0846ce12 in gtk_widget_set_usize_to_display_given_text (w=0x42270e78,
    text=0x89c897c "operate MIDI controller now", hpadding=25, vpadding=10)
    at libs/gtkmmext/gtkutils.c:37
37 gdk_string_extents (w->style->font,
Current language: auto; currently c
(gdb) backtrace
#0 0x0846ce12 in gtk_widget_set_usize_to_display_given_text (w=0x42270e78,
    text=0x89c897c "operate MIDI controller now", hpadding=25, vpadding=10)
    at libs/gtkmmext/gtkutils.c:37
0000001 0x0846ac3f in Gtkmmext::set_usize_to_display_given_text(Gtk::Widget&, char const*, int, int) (w=@0x42270ce0, text=0x89c897c "operate MIDI controller now", hpadding=25, vpadding=10)
    at libs/gtkmmext/utils.cc:32
#2 0x0845fc37 in Gtkmmext::PopUp::touch() (this=0x42270cbc) at libs/gtkmmext/popup.cc:87
#3 0x0844ea74 in Gtkmmext::UI::do_request(Gtkmmext::UI::Request*) (this=0x869ce80,
    req=0x86f0d5c) at libs/gtkmmext/gtk_ui.cc:477
0000004 0x0844eb83 in Gtkmmext::UI::send_request(Gtkmmext::UI::Request*) (this=0x869ce80,
    req=0x86f0d5c) at libs/gtkmmext/gtk_ui.cc:514
0000005 0x0844df80 in Gtkmmext::UI::touch_display(Touchable*) (this=0x869ce80, display=0x42270cd8)
    at libs/gtkmmext/gtk_ui.cc:216
#6 0x084459e6 in Gtkmmext::BarController::midicontrol_prompt() (this=0x42270c70)
    at libs/gtkmmext/barcontroller.cc:418
#7 0x08446c32 in SigC::ObjectSlot0_<void, Gtkmmext::BarController>::callback(void*) (
    d=0x4228306c) at object_slot.h:56
0000008 0x0806f0e5 in SigC::Callback0<void>::call() (this=0x4228306c) at slot.h:260
0000009 0x0806ffb7 in SigC::Signal0<void, SigC::Marshal<void> >::emit() (this=0x8a34eec)
    at basic_signal.h:193
0000010 0x0806fd79 in SigC::Signal0<void, SigC::Marshal<void> >::operator()() (this=0x8a34eec)
    at basic_signal.h:171
0000011 0x0846da3b in MIDI::Controllable::learn_about_external_control() (this=0x8a34ee8)
    at libs/midi++/midicontrollable.cc:90
0000012 0x08445901 in Gtkmmext::BarController::midi_learn() (this=0x42270c70)
    at libs/gtkmmext/barcontroller.cc:407
0000013 0x08444b46 in Gtkmmext::BarController::button_release(_GdkEventButton*) (this=0x42270c70,
---Type <return> to continue, or q <return> to quit---
    ev=0x8922f78) at libs/gtkmmext/barcontroller.cc:170
0000014 0x084469c9 in SigC::ObjectSlot1_<int, _GdkEventButton*, Gtkmmext::BarController>::callback(void*, _GdkEventButton*) (d=0x42282f9c, p1=0x8922f78) at object_slot.h:153
#15 0x08068e94 in SigC::Callback1<int, _GdkEventButton*>::call(_GdkEventButton* const&) (
    this=0x42282f9c, p1=@0xbfffebe4) at slot.h:358
0000016 0x08068e75 in Gtk::ProxySignal1<int, _GdkEventButton*, Gtk::Widget, _GtkWidget, 18>::gtk_callback(_GtkObject*, _GdkEventButton*, void*) (p1=0x8922f78, d=0x42282fb0) at proxy.h:203
#17 0x084b3ce5 in gtkmm_marshal_INT__POINTER(_GtkObject*, void (*)(), void*, _GtkArg*) (
    object=0x4228d610,
    func=0x8068e4e <Gtk::ProxySignal1<int, _GdkEventButton*, Gtk::Widget, _GtkWidget, 18>::gtk_callback(_GtkObject*, _GdkEventButton*, void*)>, func_data=0x42282fb0, args=0xbfffece0)
    at libs/gtkmm/src/gtk--/marshal.cc:240
0000018 0x40268da1 in gtk_signal_remove_emission_hook () from /usr/lib/libgtk-1.2.so.0
0000019 0x4228d610 in ?? ()
0000020 0x08068e4e in SigC::Slot1<int, _GdkEventButton*>::data() const () at scope.h:122
0000021 0x00009f15 in ?? ()
0000022 0x086d8270 in ?? ()
0000023 0x00000084 in ?? ()
Previous frame inner to this frame (corrupt stack?)
(gdb)

taybin

2007-02-15 21:40

administrator   ~0003305

Is this still an issue with the latest Ardour-2?

paul

2007-02-23 17:32

administrator   ~0003375

i deem this solved. the code has changed substantively, and the steps philicorda outlined to reproduce do not cause any problems.

Issue History

Date Modified Username Field Change
2005-03-13 17:26 lukaz New Issue
2005-03-13 17:26 lukaz E-mail => lerni@gmx.ch
2005-03-13 17:26 lukaz Name => lukas erni
2005-03-15 20:16 philicordas Note Added: 0002134
2005-03-31 02:50 paul Note Added: 0002150
2005-03-31 06:58 lukaz Note Added: 0002152
2005-04-03 18:55 philicordas Note Added: 0002164
2005-04-08 16:08 philicordas Note Added: 0002173
2007-02-15 21:40 taybin Note Added: 0003305
2007-02-23 17:32 paul Status new => resolved
2007-02-23 17:32 paul Resolution open => fixed
2007-02-23 17:32 paul Assigned To => paul
2007-02-23 17:32 paul Note Added: 0003375
2008-11-20 23:57 seablade Status resolved => closed