From: Reiner Steib <reiner.steib@gmx.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Daniel Jacobowitz <drow@false.org>, gdb@sources.redhat.com
Subject: Re: Variable "foo" is not available
Date: Sat, 02 Apr 2005 13:53:00 -0000 [thread overview]
Message-ID: <v91x9ts2tj.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <01c53768$Blat.v2.4$d52008a0@zahav.net.il> (Eli Zaretskii's message of "Sat, 02 Apr 2005 12:45:21 +0300")
On Sat, Apr 02 2005, Eli Zaretskii wrote:
> Rainer, could you please use the GDB "up" command a few times, and
> after each time type "info args" and see whether that does give you
> the arguments of the function call in that frame?
I will do this when I'm back in the office.
> Rainer, could you please tell exactly which compiler switches were
> used to build that version of Emacs?
I didn't specify any compiler related configure arguments (only
--prefix, --with-gtk and --exec-prefix) so I use the default options
from Emacs' built system:
,----[ src/Makefile ]
| CC=gcc
| CPP=gcc -E
| CFLAGS=-g -O2
| CPPFLAGS=-D_BSD_SOURCE
| LDFLAGS= -Wl,-znocombreloc -L/usr/X11R6/lib64
`----
> In any case, if Rainer could build the latest snapshot of GDB and see
> if the values of the rest of the function call arguments are printed
> (as opposed to all of them generating the "not available" message), it
> would perhaps tell us something about the underlying problem.
This problem is not reproducible. It's the first time I got those
`Variable "foo" is not available' messages when running Emacs under
gdb (see my previous reports on emacs-pretest). Is it possible to
detach from this session from gdb and re-attach it to the snapshot
gdb?
Bye, Reiner ...without any `a' in his name. ;-)
--
PGP key available http://rsteib.home.pages.de/
next prev parent reply other threads:[~2005-04-02 13:53 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-01 16:40 Reiner Steib
2005-04-01 17:19 ` Daniel Jacobowitz
2005-04-02 9:49 ` Eli Zaretskii
2005-04-02 13:53 ` Reiner Steib [this message]
2005-04-02 14:27 ` Daniel Jacobowitz
2005-04-06 16:25 ` Reiner Steib
2005-04-02 14:26 ` Daniel Jacobowitz
2005-04-02 18:17 ` Eli Zaretskii
2005-04-02 18:40 ` Daniel Jacobowitz
2005-04-02 20:58 ` Eli Zaretskii
2005-04-02 21:05 ` Daniel Jacobowitz
2005-04-04 5:14 ` Eli Zaretskii
2005-04-04 6:00 ` Mark Kettenis
2005-04-04 7:58 ` Daniel THOMPSON
2005-04-04 19:28 ` Eli Zaretskii
2005-04-04 13:37 ` Daniel Jacobowitz
2005-04-04 19:35 ` Eli Zaretskii
2005-04-04 19:41 ` Daniel Jacobowitz
2005-04-03 18:16 ` Reiner Steib
2005-04-08 11:05 ` Eli Zaretskii
2005-04-04 9:26 ` Reiner Steib
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=v91x9ts2tj.fsf@marauder.physik.uni-ulm.de \
--to=reiner.steib@gmx.de \
--cc=drow@false.org \
--cc=eliz@gnu.org \
--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