From: Klaus Zeitler <kzeitler@lucent.com>
To: gdb <gdb@sources.redhat.com>
Subject: Re: calling functions in gdb sometimes doesn't work
Date: Fri, 23 May 2003 13:13:00 -0000 [thread overview]
Message-ID: <q5g1xyperhn.fsf@lucent.com> (raw)
>>>>> "Andrew" == Andrew Cagney <ac131313@redhat.com> writes:
Andrew>
>> Hi,
>> with gdb 5.2 (Solaris 5.8) sometimes calling a function,
Andrew>
>> e.g. hello(){printf("hello\n");}, results in the following message:
>> (gdb) p hello()
Andrew>
>> The program being debugged stopped while in a function called from GDB.
>> When the function (hello) is done executing, GDB will silently
>> stop (instead of continuing to evaluate the expression containing
>> the function call).
>> When I try to continue my program it appears as if this function didn't
>> get call at all.
Andrew>
Andrew> Check which thread has stopped.
The one where I'm just at when I call a function.
Actually the message from above appears only when I've some breakpoint
defined, in which gdb would eventually run into, when I continue.
If there's no breakpoint, gdb will ignore my function call and continue the
program, but it'll show this message when I interrupt the program again.
Klaus
--
------------------------------------------
| Klaus Zeitler Lucent Technologies |
| Email: kzeitler@lucent.com |
------------------------------------------
---
Idiot, n.: A member of a large and powerful tribe whose
influence in human affairs has always been dominant and
controlling. -- Ambrose Bierce, "The Devil's Dictionary"
next reply other threads:[~2003-05-23 13:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-23 13:13 Klaus Zeitler [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-05-22 12:41 Klaus Zeitler
2003-05-22 13:52 ` Andrew Cagney
2003-05-22 15:46 ` Daniel Jacobowitz
2003-05-23 14:03 ` Klaus Zeitler
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=q5g1xyperhn.fsf@lucent.com \
--to=kzeitler@lucent.com \
--cc=gdb@sources.redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).