30 Jun
2005
30 Jun
'05
12:57 p.m.
On 6/30/05, Artemio <artemio(a)kdemail.net> wrote:
Dear friends,
thanks again for your help with my ports definition yesterday - with
it, I created a clipping booster plugin with three control ports and
it works perfectly.
However, today I added the fourth port, following all rules I learnt,
but I get the same segfaults as yesterday. If you could have a look
at the sources (attached), it would be of fantastic help for me.
Once again, please forgive me, I am a real newbie at this and things
that are very obvious for you are not such for me... But as I
understand all these bells and whistles, I will be more silent ;-)
Thanks a lot again.
Regards,
Artemiy.
Usually, the first thing I do upon a segfault is determine where it
happened using the core dump. Most of the time, my mistakes are
obvious.
Forgive me if you know all this already:
1. Compile with debugging enabled (use the -g flag to gcc)
2. Use ulimit to enable core dumps: ulimit -c unlimited
3. Run your program in the same shell as where you ran ulimit and
allow it to seg fault (it should the create a file called "core" or
"core.<pid>" where pid is the process ID (a number).
4. Use gdb to obtain a stack trace: "gdb <your program> <core
file>".
At the prompt, type "bt"
Things may be a little more complicated since you're writing a
plug-in, but the above should get you going.
HTH