public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "smaximov at yahoo dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug gdb/16201] internal error on a cygwin program linked against a DLL with no .data section Date: Thu, 21 Nov 2013 21:54:00 -0000 [thread overview] Message-ID: <bug-16201-4717-Gq2NDWzQNR@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-16201-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=16201 --- Comment #5 from Stas Maximov <smaximov at yahoo dot com> --- This appears to be COFF-PE specific. It is not likely to be repeatable on a platform other than 32-bit Cygwin. If it helps, here is the result of coff-pe-read trace: ... $ gdb test1 (gdb) set debug coff-pe-read 1 (gdb) run Starting program: /home/user/test/test1.exe [New Thread 8076.0x29e8] Export RVA for dll "/cygdrive/c/Windows/system32/ntdll.dll" is in section ".text" DLL "ntdll" has 2025 export entries, base=1 Finished reading "ntdll", exports 2025, forwards 0, total 2025/2025. Export RVA for dll "/cygdrive/c/Windows/syswow64/kernel32.dll" is in section ".text" DLL "KERNEL32" has 1364 export entries, base=1 Unable to find function "AddDllDirectory" in dll "api-ms-win-core-libraryloader-l1-1-0", forward of "AddDllDirectory" in dll "KERNEL32" Unable to find function "CreateRemoteThreadEx" in dll "api-ms-win-core-processthreads-l1-1-0", forward of "CreateRemoteThreadEx" in dll "KERNEL32" Unable to find function "DeleteProcThreadAttributeList" in dll "api-ms-win-core-processthreads-l1-1-0", forward of "DeleteProcThreadAttributeList" in dll "KERNEL32" Unable to find function "GetLogicalProcessorInformationEx" in dll "api-ms-win-core-sysinfo-l1-1-0", forward of "GetLogicalProcessorInformationEx" in dll "KERNEL32" Unable to find function "InitializeProcThreadAttributeList" in dll "api-ms-win-core-processthreads-l1-1-0", forward of "InitializeProcThreadAttributeList" in dll "KERNEL32" Unable to find function "OpenProcessToken" in dll "api-ms-win-core-processthreads-l1-1-0", forward of "OpenProcessToken" in dll "KERNEL32" Unable to find function "OpenThreadToken" in dll "api-ms-win-core-processthreads-l1-1-0", forward of "OpenThreadToken" in dll "KERNEL32" Unable to find function "RemoveDllDirectory" in dll "api-ms-win-core-libraryloader-l1-1-0", forward of "RemoveDllDirectory" in dll "KERNEL32" Unable to find function "SetDefaultDllDirectories" in dll "api-ms-win-core-libraryloader-l1-1-0", forward of "SetDefaultDllDirectories" in dll "KERNEL32" Unable to find function "SetThreadToken" in dll "api-ms-win-core-processthreads-l1-1-0", forward of "SetThreadToken" in dll "KERNEL32" Unable to find function "SetWaitableTimerEx" in dll "api-ms-win-core-threadpool-l1-1-0", forward of "SetWaitableTimerEx" in dll "KERNEL32" Unable to find function "SystemTimeToTzSpecificLocalTimeEx" in dll "kernelbase", forward of "SystemTimeToTzSpecificLocalTimeEx" in dll "KERNEL32" Unable to find function "TzSpecificLocalTimeToSystemTimeEx" in dll "kernelbase", forward of "TzSpecificLocalTimeToSystemTimeEx" in dll "KERNEL32" Unable to find function "UpdateProcThreadAttribute" in dll "api-ms-win-core-processthreads-l1-1-0", forward of "UpdateProcThreadAttribute" in dll "KERNEL32" Finished reading "KERNEL32", exports 1282, forwards 68, total 1350/1364. Export RVA for dll "/cygdrive/c/Windows/syswow64/KERNELBASE.dll" is in section ".text" DLL "KERNELBASE" has 633 export entries, base=1 Finished reading "KERNELBASE", exports 576, forwards 57, total 633/633. Export RVA for dll "/home/user/test/icudt49.dll" is in section ".rdata" DLL "icudt49" has 1 export entries, base=1 /netrel/src/gdb-7.6.50-4/gdb/minsyms.c:885: internal-error: sect_index_data not initialized A problem internal to GDB has been detected, further debugging may prove unreliable. Quit this debugging session? (y or n) y /netrel/src/gdb-7.6.50-4/gdb/minsyms.c:885: internal-error: sect_index_data not initialized A problem internal to GDB has been detected, further debugging may prove unreliable. Create a core file of GDB? (y or n) n -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2013-11-21 21:54 UTC|newest] Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-11-21 19:29 [Bug gdb/16201] New: " smaximov at yahoo dot com 2013-11-21 20:37 ` [Bug gdb/16201] " smaximov at yahoo dot com 2013-11-21 21:09 ` smaximov at yahoo dot com 2013-11-21 21:30 ` tromey at redhat dot com 2013-11-21 21:36 ` smaximov at yahoo dot com 2013-11-21 21:39 ` tromey at redhat dot com 2013-11-21 21:54 ` smaximov at yahoo dot com [this message] 2013-11-21 22:01 ` tromey at redhat dot com 2013-11-21 22:04 ` smaximov at yahoo dot com 2013-11-22 15:58 ` tromey at redhat dot com 2013-11-22 23:48 ` smaximov at yahoo dot com 2013-11-23 17:23 ` keiths at redhat dot com 2013-11-25 18:30 ` smaximov at yahoo dot com 2013-11-25 21:33 ` tromey at redhat dot com 2013-11-25 21:56 ` tromey at redhat dot com 2013-11-26 0:21 ` smaximov at yahoo dot com 2013-11-26 2:20 ` muller at sourceware dot org 2013-11-26 3:13 ` smaximov at yahoo dot com 2013-11-27 0:04 ` smaximov at yahoo dot com 2013-12-02 11:33 ` asmwarrior at gmail dot com 2013-12-21 0:49 ` smaximov at yahoo dot com 2013-12-21 1:02 ` asmwarrior at gmail dot com 2023-12-09 12:46 ` ssbssa at sourceware dot org
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=bug-16201-4717-Gq2NDWzQNR@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=gdb-prs@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: linkBe 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; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).