Date: Tue, 04 Dec 2012 09:47:37 -0500
From: Alan Boudreault <boudreault.alan@gmail.com>
CC: 13057@debbugs.gnu.org
I've tried 2 differents remote programs and got the same bug. However, I
haven't seen the same behavior debugging remotely. Also, it seems to be
only the first gdb process I run that has that behavior. If I open a
first gdb process... I see the bug.... and If I open another gdb process
there is no more list command executed and I can debug properly.
This command comes from the function gdb-place-breakpoints (see
gdb-mi.el). From cursory reading of that function, it looks like it
issues this command when it cannot glean the file name from what GDB
replies. Maybe you could try upgrading to a newer GDB, because it
could be a GDB problem that triggers this command.