For these symbols, they actually point to the symbol's IAT entry instead, which obviously is different from the symbol itself (which is imported from a different module and doesn't exist in this one).
Omitting this symbol helps gdb inspect automatically imported symbols, see https://sourceware.org/bugzilla/show_bug.cgi?id=24574 for discussion on the matter.
Surprisingly, those extra symbols don't seem to be an issue for gdb when the sources have been built with clang, only with gcc. The actual logic in gdb that this depends on still is unknown, but omitting these symbols from the symbol table is the right thing to do in any case.
While this isn't a normal bugfix, it fixes one issue reported to me by a user, and the fix is very straightforward, so maybe it still could qualify for the release branch @hans?