From: "Luís Russo" <lsr@vinci.inesc-id.pt>
To: gdb@sources.redhat.com
Cc: "Luís Russo" <lsr@vinci.inesc-id.pt>
Subject: gdb calls bypassbreakpoints
Date: Fri, 23 Jul 2004 15:05:00 -0000 [thread overview]
Message-ID: <A0F93804-DCAD-11D8-B1A4-000A957774FE@algos.inesc-id.pt> (raw)
Hi,
I am debugging a C file. I set some breakpoints inside my C functions
that print what's going on. The breakpoints have a list of commands
that do some prints and some continues.
Sometimes I want to call the functions with different arguments from
those hardcoded in C, and I use the call function.
But then I get this message:
The program being debugged stopped while in a function called from GDB.
When the function (minSphere) is done executing, GDB will silently
stop (instead of continuing to evaluate the expression containing
the function call)
Is there a way to stop this behavior and make gdb act as if the call
had came from the C file?
Thanks,
Luís Russo
INESC
Rua Alves Redol n 9, 1049-001 LISBOA, PORTUGAL
tel:+351 21 3100272
email:lsr@algos.inesc-id.pt
next reply other threads:[~2004-07-23 13:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-23 15:05 Luís Russo [this message]
2004-07-24 7:53 ` mec.gnu
2004-07-25 0:03 ` Eli Zaretskii
2004-07-26 21:21 ` Andrew Cagney
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=A0F93804-DCAD-11D8-B1A4-000A957774FE@algos.inesc-id.pt \
--to=lsr@vinci.inesc-id.pt \
--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