From: "Joël Krähemann" <weedlight@gmail.com>
To: gdb@sourceware.org
Subject: gdb function signature differs from declaration
Date: Fri, 14 Mar 2014 12:11:00 -0000 [thread overview]
Message-ID: <1394799086.4203.8.camel@debian> (raw)
The last stack entry #0 is missing a parameter what could cause this?
AgsRecallID*
ags_channel_recursive_play_init(AgsChannel *channel, gint stage,
gboolean arrange_recall_id,
gboolean duplicate_templates, gboolean playback, gboolean sequencer,
gboolean notation,
gboolean resolve_dependencies,
AgsRecallID *recall_id)
#0 0x0000000000481b1a in ags_channel_recursive_play_init
(channel=channel@entry=0x7fffdc0c8e20,
arrange_recall_id=arrange_recall_id@entry=0,
duplicate_templates=duplicate_templates@entry=0,
playback=playback@entry=0, sequencer=sequencer@entry=1,
notation=notation@entry=0,
resolve_dependencies=resolve_dependencies@entry=0,
recall_id=0x7fffd60baea0) at ./src/ags/audio/ags_channel.c:3389
#1 0x0000000000466cf7 in ags_audio_recursive_play_init
(audio=0x7fffdc051ba0, playback=playback@entry=0,
sequencer=sequencer@entry=1, notation=notation@entry=0)
at ./src/ags/audio/ags_audio.c:2175
#2 0x00000000004568ea in ags_init_audio_launch (task=<optimized out>)
at ./src/ags/audio/task/ags_init_audio.c:152
#3 0x00007ffff4bca367 in ?? ()
from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#4 0x00007ffff4be2df8 in g_signal_emit_valist ()
from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#5 0x00007ffff4be3a52 in g_signal_emit ()
from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#6 0x000000000044c906 in ags_task_launch (task=0x7fffd60b12c0)
at ./src/ags/audio/ags_task.c:164
#7 0x00000000004b1a9d in ags_task_thread_run (thread=0x9340b0)
at ./src/ags/thread/ags_task_thread.c:229
#8 0x00007ffff4bca2df in ?? ()
from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#9 0x00007ffff4be2df8 in g_signal_emit_valist ()
from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#10 0x00007ffff4be3a52 in g_signal_emit ()
from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
#11 0x00000000004af406 in ags_thread_run (thread=0x9340b0)
at ./src/ags/thread/ags_thread.c:1716
#12 0x00000000004af797 in ags_thread_loop (ptr=<optimized out>)
at ./src/ags/thread/ags_thread.c:1639
#13 0x00007ffff377a062 in start_thread (arg=0x7fffe708f700) at
pthread_create.c:312
#14 0x00007ffff34aea3d in clone ()
at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111
next reply other threads:[~2014-03-14 12:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-14 12:11 Joël Krähemann [this message]
2014-03-14 18:08 ` Tom Tromey
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1394799086.4203.8.camel@debian \
--to=weedlight@gmail.com \
--cc=gdb@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox