[LAD] New SVN version of LV2:AVW - Crashes Ingen

2012-05-18 Thread Aurélien Leblond
 I have been trying to use GDB to debug this issue.
 Problem is, as the program crashing is Ingen, I get the information as to
 where it crashes in Ingen, not where the problem lies in my plugin.

 Would anybody have any ideas as to how to tacke this issue?


 If the plugin runs in a different process,
 it may be necessary to attach that process to gdb.
 Don't forget to compile with debug enabled.

Thanks for that.

I have tried to approach so far:
* gdb --args ingen -eg
I would then run my plugin, remove it, Ingen would crash, but I would
get the information as to why Ingen crashed.
I'm not even sure that GDB would see that it should debug the vco2.so as well

* gdb vco2.so
(vco2.so being the name of my plugin)
Now I start Ingen, get the PID, and use
attach 15674
in gdb (I tried with or without the plugin running).
I get the following error message in GDB:
   (gdb) attach 15764B
   Attaching to program:
/home/blablack/src/avw.lv2/build/avw.lv2/vco2.so, process 15764
   Could not attach to process.  If your uid matches the uid of the target
   process, check the setting of /proc/sys/kernel/yama/ptrace_scope, or try
   again as the root user.  For more details, see /etc/sysctl.d/10-ptrace.conf
   ptrace: Operation not permitted.

I guess GDB is looking for the vco2.so when attaching...


So what stupid thing am I doing?

Thanks in advance for the help,

Aurélien
___
Linux-audio-dev mailing list
Linux-audio-dev@lists.linuxaudio.org
http://lists.linuxaudio.org/listinfo/linux-audio-dev


Re: [LAD] New SVN version of LV2:AVW - Crashes Ingen

2012-05-15 Thread Aurélien Leblond
Hi everyone,

I have been trying to use GDB to debug this issue.
Problem is, as the program crashing is Ingen, I get the information as to
where it crashes in Ingen, not where the problem lies in my plugin.

Would anybody have any ideas as to how to tacke this issue?

Thanks in advance for any help,

Aurélien

On Sat, May 12, 2012 at 5:56 PM, Aurélien Leblond blabl...@gmail.comwrote:

 Hi everyone,

 I posted a new version of the LV2:AVW on the SVN:
 svn checkout svn://svn.code.sf.net/p/avwlv2/code/trunk avwlv2-code

 Unfortunately, it is crippled with a bug that I can't for the life of me
 fix!

 The scenario is as followed:
 - Open Ingen
 - Add one of these plugins
 - Remove it and Ingen crashes

 That other scenario would crash it too:
 - Open Ingen
 - Add one of these plugins
 - Add any other plugin (I use MDA)
 - Remove the MDA plugin, and Ingen crashes.

 Now, I don't think the issue lies in Ingen as I can add/remove any
 instances of the MDA plugins for example.
 But JALV or Ardour don't see to have this issue...

 I'm really looking for some help guys, because I have been trying to debug
 that one for few weeks now without much success.

 Thanks in advance foranything!

 Aurélien

___
Linux-audio-dev mailing list
Linux-audio-dev@lists.linuxaudio.org
http://lists.linuxaudio.org/listinfo/linux-audio-dev


Re: [LAD] New SVN version of LV2:AVW - Crashes Ingen

2012-05-15 Thread Emanuel Rumpf
2012/5/15 Aurélien Leblond blabl...@gmail.com:
 Hi everyone,

 I have been trying to use GDB to debug this issue.
 Problem is, as the program crashing is Ingen, I get the information as to
 where it crashes in Ingen, not where the problem lies in my plugin.

 Would anybody have any ideas as to how to tacke this issue?


If the plugin runs in a different process,
it may be necessary to attach that process to gdb.
Don't forget to compile with debug enabled.


(gdb) help attach
Attach to a process or file outside of GDB.
This command attaches to another target, of the same type as your last
target command (info files will show your target stack).
The command may take as argument a process id or a device file.
For a process id, you must have permission to send the process a signal,
and it must have the same effective uid as the debugger.
When using attach with a process id, the debugger finds the
program running in the process, looking first in the current working
directory, or (if not found there) using the source file search path
(see the directory command).  You can also use the file command
to specify the program, and to load its symbol table.


-- 
E.R.
___
Linux-audio-dev mailing list
Linux-audio-dev@lists.linuxaudio.org
http://lists.linuxaudio.org/listinfo/linux-audio-dev