[Csnd] trying again
Date | 2012-11-12 12:02 |
From | jpff@cs.bath.ac.uk |
Subject | [Csnd] trying again |
----- This is a copy of the message, including all the headers. ------ ate: Mon, 12 Nov 2012 08:32:32 -0000 Subject: Re: [Csnd] Re: Csound on Embedded Linux (BeagleBone) From: jpff@cs.bath.ac.uk To: csound@lists.bath.ac.uk > We recognise that sf_open() is returning null, otherwise we would not have > that printout and exit. But what confuses us is the fact that the filename > string becomes NULL after the sf_open() return. This is not what I would > expect and points to a probable issue with libsndfile in your build. > > Generally, when libsndfile cannot open the file, say because it does not > have the permission, it will return NULL and we can print out the > filename, which is what the code is supposed to do. > > Victor > Looking at rhe sources of libsndfile I cannot see how it is to blame. The path variable is declared const and it is copied in sf_open bur never written. Might be interesting to seewhat is in the sndfile_log |
Date | 2012-11-12 12:55 |
From | Victor Lazzarini |
Subject | Re: [Csnd] trying again |
yes, I agree with this. So another option is a memory leak and somehow the actions of sf_open() overwrite the filename. On 12 Nov 2012, at 12:02, jpff@cs.bath.ac.uk wrote: > ----- This is a copy of the message, including all the headers. ------ > ate: Mon, 12 Nov 2012 08:32:32 -0000 > Subject: Re: [Csnd] Re: Csound on Embedded Linux (BeagleBone) > From: jpff@cs.bath.ac.uk > To: csound@lists.bath.ac.uk > >> We recognise that sf_open() is returning null, otherwise we would not have >> that printout and exit. But what confuses us is the fact that the filename >> string becomes NULL after the sf_open() return. This is not what I would >> expect and points to a probable issue with libsndfile in your build. >> >> Generally, when libsndfile cannot open the file, say because it does not >> have the permission, it will return NULL and we can print out the >> filename, which is what the code is supposed to do. >> >> Victor >> > > Looking at rhe sources of libsndfile I cannot see how it is to blame. The > path variable is declared const and it is copied in sf_open bur never > written. Might be interesting to seewhat is in the sndfile_log > > > > > > > > > > > > > Send bugs reports to the Sourceforge bug tracker > https://sourceforge.net/tracker/?group_id=81968&atid=564599 > Discussions of bugs and features can be posted here > To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound" > Dr Victor Lazzarini Senior Lecturer Dept. of Music NUI Maynooth Ireland tel.: +353 1 708 3545 Victor dot Lazzarini AT nuim dot ie |
Date | 2012-11-12 12:57 |
From | jpff@cs.bath.ac.uk |
Subject | Re: [Csnd] trying again |
> yes, I agree with this. So another option is a memory leak and somehow the > actions of sf_open() overwrite the filename. > I rather suspect a memory problem -- seems to have the symptoms. I suppose there is no valgrid on this device? That seems like the next step |
Date | 2012-11-12 14:02 |
From | Victor Lazzarini |
Subject | Re: [Csnd] trying again |
It's hard to debug without a device. I expect valgrind to be available, after all this is linux. We can ask him to get it and run csound under it. Victor On 12 Nov 2012, at 12:57, jpff@cs.bath.ac.uk wrote: >> yes, I agree with this. So another option is a memory leak and somehow the >> actions of sf_open() overwrite the filename. >> > > I rather suspect a memory problem -- seems to have the symptoms. I > suppose there is no valgrid on this device? That seems like the next step > > > > Send bugs reports to the Sourceforge bug tracker > https://sourceforge.net/tracker/?group_id=81968&atid=564599 > Discussions of bugs and features can be posted here > To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound" > Dr Victor Lazzarini Senior Lecturer Dept. of Music NUI Maynooth Ireland tel.: +353 1 708 3545 Victor dot Lazzarini AT nuim dot ie |
Date | 2012-11-12 14:45 |
From | Steven Yi |
Subject | Re: [Csnd] trying again |
Another possibility is if William could put the device on the internet and have it open for remote login, one of us could possibly ssh into it to try some things out. On Mon, Nov 12, 2012 at 2:02 PM, Victor Lazzarini |