From: Reiner Steib <reinersteib+gmane@imap.cc>
Cc: emacs-devel@gnu.org
Subject: Re: SEGV in enable_glyph_matrix_rows
Date: Fri, 24 Sep 2004 14:41:44 +0200 [thread overview]
Message-ID: <v93c17bzzr.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <E1CAosi-00011t-63@fencepost.gnu.org> (Richard Stallman's message of "Fri, 24 Sep 2004 08:08:56 -0400")
On Fri, Sep 24 2004, Richard Stallman wrote:
> Can you investigate the data structure in this matrix that
> is being cleared, and see what's invalid in it?
> The backtrace suggests nothing except that you need to look
> at that data.
Sorry, I'm not familiar with debugging C programs. I don't know which
data I need to look at and how (although I have read etc/DEBUG).
Unless someone can tell me what to type at the gdb prompt, I'm afraid
I cannot give more useful information.
Maybe I already did something wrong by using `pr' here:
--8<---------------cut here---------------start------------->8---
(gdb) p matrix
$1 = (struct glyph_matrix *) 0x9010000
(gdb) pr
Program received signal SIGPIPE, Broken pipe.
0x4070b3a8 in write () from /lib/libc.so.6
The program being debugged was signaled while in a function called from GDB.
GDB remains in the frame where the signal was received.
To change this behavior use "set unwindonsignal on"
Evaluation of the expression containing the function (debug_print) will be abandoned.
(gdb) xtype
Argument to arithmetic operation not a number or boolean.
(gdb) p matrix
No symbol "matrix" in current context.
--8<---------------cut here---------------end--------------->8---
Bye, Reiner.
--
,,,
(o o)
---ooO-(_)-Ooo--- | PGP key available | http://rsteib.home.pages.de/
next prev parent reply other threads:[~2004-09-24 12:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <v9r7ot2guh.fsf@marauder.physik.uni-ulm.de>
2004-09-24 12:08 ` SEGV in enable_glyph_matrix_rows Richard Stallman
2004-09-24 12:41 ` Reiner Steib [this message]
2004-09-24 13:44 ` Andreas Schwab
2004-09-25 15:34 ` Richard Stallman
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=v93c17bzzr.fsf@marauder.physik.uni-ulm.de \
--to=reinersteib+gmane@imap.cc \
--cc=Reiner.Steib@gmx.de \
--cc=emacs-devel@gnu.org \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).