From: Roland Zerek <rolandz@poczta.fm>
To: Kris Warkentin <kewarken@qnx.com>
Cc: gdb@sources.redhat.com
Subject: Re: Breakpoints in the library code
Date: Wed, 30 Jun 2004 18:53:00 -0000 [thread overview]
Message-ID: <40E2FEC4.3070503@poczta.fm> (raw)
In-Reply-To: <40E2FC82.4020008@qnx.com>
Użytkownik Kris Warkentin napisał:
> You should hit 'reply all' when you reply to me - that way you response
> goes to the mailing list as well. You might get help from someone else
Oops.... Sorry - did not notify to whom I am writting... I always just
simply reply to sender when sending to mailing lists since the sender is
usually the mailserver...
> as well. Question: did you try break wxXmlResource<tab> to see which
> members gdb thinks are available for breakpoints?
You mean that gdb is capable to autocomplete the name? I did not know it.
Will try.
>>> Hmm. Well, if it's not recognizing the name of the method, you might
>>> want to try setting the breakpoint by filename:line number. (ie
>>> foo.cc:73). If that works, then when you hit the breakpoint, you can
>>> do a backtrace and see what gdb thinks the name of the method is.
>> It works quite well, thanks. However backtrace gives me the same
>> method name as expected...
>>
>> Another question is: why command line debugger works perfectly and GUI
>> frontends not... Are there some incompatibilities in gdb api or the
>> way the insight or ddd comunicates with gdb is incorrect? Sorry for
>> possibly trivial question but I am not gdb expert.
--
Roland
r o l a n d z (at) poczta fm
prev parent reply other threads:[~2004-06-30 17:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-30 10:44 Roland Zerek
2004-06-30 13:28 ` Kris Warkentin
[not found] ` <40E2B3B6.6070802@poczta.fm>
2004-06-30 14:54 ` Kris Warkentin
[not found] ` <40E2C6CE.4070703@poczta.fm>
2004-06-30 16:04 ` Kris Warkentin
[not found] ` <40E2E20A.7070000@poczta.fm>
2004-06-30 17:56 ` Kris Warkentin
2004-06-30 18:53 ` Roland Zerek [this message]
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=40E2FEC4.3070503@poczta.fm \
--to=rolandz@poczta.fm \
--cc=gdb@sources.redhat.com \
--cc=kewarken@qnx.com \
/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