From: Pedro Alves <pedro_alves@portugalmail.pt>
To: Bogdan Slusarczyk <bodzio131@op.pl>
Cc: gdb@sourceware.org
Subject: Re: gdb 6.7.50.20071127 - few problems
Date: Fri, 14 Dec 2007 00:53:00 -0000 [thread overview]
Message-ID: <4761D3EB.50405@portugalmail.pt> (raw)
In-Reply-To: <475FC54D.1040200@op.pl>
Bogdan Slusarczyk wrote:
> Hi,
> I've tried to use gdb6.7.50.20071127 (mingw). I noticed few problems (in
> comparison with gdb6.7.1).
> 1) after attaching to process 'info shared' returns: "No shared
> libraries loaded at this time" (gdb6.7.1 returns few libraries)
I can reproduce this when attaching without specifying the executable
'gdb --pid $pid', and can't if I do specify it. I take it that's
what you mean.
> 2) debugged process has loaded shared library using LoadLibrary, and I
> cannot set breakpoint in this library. I get: "No symbol table is
> loaded. Use the "file" command" (using gdb6.7.1 I can set breakpoint
> without problem).
I haven't tried to reproduce this, but from the description, it
either,
looks like the same problem -- GDB should have at least
minimal symbols from the loaded dlls (extracted from the
dll's export table) ; if it didn't find the dlls, and you didn't
pass a symbol file on the command line, there will be no symbol
table loaded
or looks like related to PR2368 and/or PR2369.
> Why I have to use 'file' command (and 'symbol-file' too)? It works with
> mentioned commands but I'm wondering it's intended behaviour or bug?
>
Bug.
Could you open a bug report for 1) ?
(Also, when reporting win32 bugs, it would be nice to also
test it on a cygwin build -- nice, but not required.)
--
Pedro Alves
next prev parent reply other threads:[~2007-12-14 0:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-12 11:26 Bogdan Slusarczyk
2007-12-14 0:53 ` Pedro Alves [this message]
2007-12-15 15:38 ` Bogdan Slusarczyk
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=4761D3EB.50405@portugalmail.pt \
--to=pedro_alves@portugalmail.pt \
--cc=bodzio131@op.pl \
--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