From: Gary Funck <gary@intrepid.com>
To: GDB List <gdb@sources.redhat.com>
Subject: SGI/Irix: how to call procedure from GDB?
Date: Mon, 19 Nov 2007 04:30:00 -0000 [thread overview]
Message-ID: <20071119043012.GB23963@intrepid.com> (raw)
I'm trying to debug a problem in gcc using gdb (6.7.1)
on SGI/Irix 6.5. GCC has been compiled with GCC 3.3
with '-g -O0' switches. After hitting a breakpoint,
I try executing "p debug_tree(exp)" (via the gcc supplied
macro, "pt"), but instead, GDB issues the following somewhat
cryptic diagnostic:
The program being debugged stopped while in a function called from GDB.
When the function (debug_tree) is done executing, GDB will silently
stop (instead of continuing to evaluate the expression containing
the function call).
Any suggestions on what might've happened here, and what I
need to do to get GDB to to run the "debug_tree()" procedure?
thanks,
- Gary
(Output excerpted below.)
-------------------------
Breakpoint 1, fancy_abort (file=0x10b75720 "/upc/dev/gary/gcc-upc-4-2/src/gcc/expr.c",
line=6882, function=0x10b75f58 "expand_expr_real_1")
at /upc/dev/gary/gcc-upc-4-2/src/gcc/diagnostic.c:642
642 internal_error ("in %s, at %s:%d", function, trim_filename (file), line);
(gdb) up
#1 0x1031b788 in expand_expr_real_1 (exp=0x4200230, target=0x0, tmode=DImode,
modifier=EXPAND_INITIALIZER, alt_rtl=0x0)
at /upc/dev/gary/gcc-upc-4-2/src/gcc/expr.c:6882
6882 || TREE_CODE (exp) == FUNCTION_DECL);
(gdb) l
6877 context = decl_function_context (exp);
6878 gcc_assert (!context
6879 || context == current_function_decl
6880 || TREE_STATIC (exp)
6881 /* ??? C++ creates functions that are not TREE_STATIC. */
6882 || TREE_CODE (exp) == FUNCTION_DECL);
6883
6884 /* This is the case of an array whose size is to be determined
6885 from its initializer, while the initializer is still being parsed.
6886 See expand_decl. */
(gdb) p exp
$1 = (tree) 0x4200230
(gdb) pt
Breakpoint 1, fancy_abort (file=0x10b75720 "/upc/dev/gary/gcc-upc-4-2/src/gcc/expr.c",
line=6882, function=0x10b75f58 "expand_expr_real_1")
at /upc/dev/gary/gcc-upc-4-2/src/gcc/diagnostic.c:642
642 internal_error ("in %s, at %s:%d", function, trim_filename (file), line);
The program being debugged stopped while in a function called from GDB.
When the function (debug_tree) is done executing, GDB will silently
stop (instead of continuing to evaluate the expression containing
the function call).
next reply other threads:[~2007-11-19 4:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-19 4:30 Gary Funck [this message]
[not found] ` <B0D822BFECD50F4991F2516EA50F273C0367C768@NT-IRVA-0752.brcm.ad.broadcom.com>
2007-11-19 15:03 ` Gary Funck
2007-11-19 17:23 ` Joel Brobecker
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=20071119043012.GB23963@intrepid.com \
--to=gary@intrepid.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).