Note that there are some explanatory texts on larger screens.

plurals
  1. POStepping Over in Emacs GDB
    primarykey
    data
    text
    <p>I'm having some trouble stepping over in GDB. I've built an example program from the ffmpeg library with debug symbols on and stripping off. Although I configured the ffmpeg library to static and explicitly disabled shared, it looks like the program I'm debugging is linking dynamically, since its file size is only 99kB. I don't know that this is the issue but thought to mention it.</p> <p>After I set and hit a breakpoint in av_seek_frame, I use the 'next' command to step over. However, this steps into the first function within av_seek_frame(), as you can see below. Furthermore if a do a second 'next', the backtrace looses track of where it is. Am I set up wrong? How can I step over? I should note I double checked that 'set step-mode off' is off as the default (as I believe this will break at the first piece of code without debug info.)</p> <pre><code>Breakpoint 1, av_seek_frame (s=0x16429000, stream_index=0, timestamp=29727438, flags=0) at l (gdb) list 1648 1649 return 0; 1650 } 1651 1652 int av_seek_frame(AVFormatContext *s, int stream_index, int64_t timestamp, int flags 1653 { 1654 int ret; 1655 AVStream *st; 1656 1657 ff_read_frame_flush(s); (gdb) next ff_read_frame_flush (s=0x16429000) at libavformat/utils.c:1248 (gdb) list 1243 1244 /** 1245 * Flush the frame reader. 1246 **/ 1247 void ff_read_frame_flush(AVFormatContext *s) 1248 { 1249 AVStream *st; 1250 int i, j; 1251 1252 flush_packet_queue(s); (gdb) next ff_read_frame_flush (s=0x16429000) at libavformat/utils.c:1252 (gdb) where #0 ff_read_frame_flush (s=0x16429000) at libavformat/utils.c:1252 #1 0x00000000 in ?? () </code></pre>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload