2 Feb
2015
2 Feb
'15
1:45 a.m.
When exporting a session ardour (3.5) crashed and everything (Ubuntu
Studio 14.04) froze.
I had to open an "emergency terminal" (ctrl-alt-f#) to kill and reboot,
and didn't manage to copy the error message. Still I believe I can find
it in some logs, but where to find the log?
Oh, and when Ardour loaded the session after reboot it was with this
[ERROR]: could not reconstitute MementoCommand from
XMLNode. object
type = ARDOUR::AutomationList id = 21170
I suspect the reason for the crash was that I tried to give the export
file a new name not already on disk.
This should probably be in the Ardour forums, I know. I intend to
register there at some later time...
Alf
2 Feb
2 Feb
11:04 a.m.
On Mon, 02 Feb 2015 01:45:47 +0100, Alf Haakon Lund wrote:
Still I believe I can find it in some logs, but where
to find the log?
Hi Alf,
if applications started by the user or session autostart cause warnings
and errors for the current user session, they are often written to
~/.xsession-errors
the messages for the user session you run before were written to
~/.xsession-errors.old
You also could try
strace -o ardour.log -p $(pidof ardour)
To be honest, I never started strace for an app _after_ an issue
appeared. I don't know, if this does give useful output.
Regards,
Ralf
3 Feb
3 Feb
1:05 a.m.
On 02. feb. 2015 11:02, Ralf Mardorf wrote:
On Mon, 02 Feb 2015 01:45:47 +0100, Alf Haakon Lund
wrote:
Thanks for chiming in! Though it seems to me your suggestions mainly
deal with system-wide errors. I was specifically trying to find Ardour's
'crash message' - which I saw on screen, but didn't think to write down...
strace doesn't do much useful for me, though, saying
Still I believe I can find it in some logs, but
where to find the log?
Hi Alf,
if applications started by the user or session autostart cause warnings
and errors for the current user session, they are often written to
~/.xsession-errors
the messages for the user session you run before were written to
~/.xsession-errors.old
You also could try
strace -o ardour.log -p $(pidof ardour)
To be honest, I never started strace for an app _after_ an issue
appeared. I don't know, if this does give useful output. strace: attach: ptrace(PTRACE_ATTACH, ...): No such
process
Alf
4:16 a.m.
On Sun, Feb 1, 2015 at 7:45 PM, Alf Haakon Lund <alf(a)mellomrommet.no> wrote:
When exporting a session ardour (3.5) crashed and
everything (Ubuntu
Studio 14.04) froze.
I had to open an "emergency terminal" (ctrl-alt-f#) to kill and reboot,
and didn't manage to copy the error message. Still I believe I can find it
in some logs, but where to find the log?
Oh, and when Ardour loaded the session after reboot it was with this
[ERROR]: could not reconstitute MementoCommand from XMLNode. object
There are no "log files".
You can generally ignore most ERROR messages in terms of useful
information. The message above is particularly uninformative from a user
perspective.
Crashes in Ardour and ways to figure out what is happening are described at
http://ardour.org/debugging_ardour
type = ARDOUR::AutomationList id = 21170
I suspect the reason for the crash was that I tried to give the export
file a new name not already on disk.
This should probably be in the Ardour forums, I know. I intend to register
there at some later time...
4:38 a.m.
On Mon, 2 Feb 2015 22:16:55 -0500, Paul Davis wrote:
There are no "log files".
You can generally ignore most ERROR messages in terms of useful
information. The message above is particularly uninformative from a
user perspective.
Crashes in Ardour and ways to figure out what is happening are
described at http://ardour.org/debugging_ardour
That is real debugging and the OP perhaps is aware how to do this, to
file a bug report with GDB output, but assumed the OP wants to know what
happens, if during a production the version of Ardour without debug
symbols crashes. What to do then?
I don't know what to do.
It might be completely useless, but perhaps I would try this
http://lists.linuxaudio.org/pipermail/linux-audio-user/2015-February/100663…
Perhaps strace with additional options.
3609
days inactive
3610
days old
linux-audio-user@lists.linuxaudio.org
4 comments
3 participants
participants (3)
-
Alf Haakon Lund -
Paul Davis -
Ralf Mardorf