all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Bob Rogers <rogers-emacs@rgrjr.dyndns.org>
To: Eli Zaretskii <eliz@gnu.org>, Andreas Schwab <schwab@suse.de>
Cc: lekktu@gmail.com, emacs-devel@gnu.org
Subject: Re: segfault in system-process-attributes on GNU/Linux
Date: Sat, 23 Aug 2008 15:12:22 -0400	[thread overview]
Message-ID: <18608.24854.369097.535535@rgrjr.rgrjr.dyndns.org> (raw)
In-Reply-To: <umyj339zw.fsf@gnu.org>

   From: Andreas Schwab <schwab@suse.de>
   Date: Sat, 23 Aug 2008 20:05:29 +0200

   Bob Rogers <rogers-emacs@rgrjr.dyndns.org> writes:

   > Interesting.  When I evaluate:
   >
   > 	(system-process-attributes (emacs-pid))
   >
   > on my GNU/Linux system (openSUSE 10.2, kernel 2.6.18.2) using emacs
   > updated from trunk a few minutes ago, I get the segfault shown below.

   Fixed.

   Andreas.

Excellent; it works for me now.  Thanks.

   ================
   From: Eli Zaretskii <eliz@gnu.org>
   Date: Sat, 23 Aug 2008 20:40:51 +0300

   I cannot reproduce this on a GNU/Linux machine . . .

   I wonder how it can crash.  But then optimized builds tend to lie
   about line numbers.

I wondered, too, but can't seem to compile emacs with enough debugging
information; it finds the source file (at the same place you showed),
but doesn't even have debugging symbols:

	(gdb) p cmdsize
	No symbol "cmdsize" in current context.
	(gdb) 

I remember discussion of CFLAGS options for debugging, but can't find
the thread now.  I thought some writeup had been added to INSTALL.CVS or
"(emacs) Bugs", but can't find it there, either.

   In any case, any hints you may have for future debugging use would be
greatly appreciated.

					-- Bob (not a C programmer, but
					   might be able to play one on TV)




  reply	other threads:[~2008-08-23 19:12 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-09 21:13 File Owner and Group ID on Windows Eli Zaretskii
2008-08-21  1:27 ` Juanma Barranquero
2008-08-21  1:35   ` Lennart Borgman (gmail)
2008-08-21  1:56     ` Juanma Barranquero
2008-08-21  5:44   ` Eli Zaretskii
2008-08-21 14:14     ` Juanma Barranquero
2008-08-21 16:37       ` Eli Zaretskii
2008-08-22 10:34         ` Juanma Barranquero
2008-08-22 10:35           ` Juanma Barranquero
2008-08-23 16:10             ` segfault in system-process-attributes on GNU/Linux Bob Rogers
2008-08-23 17:40               ` Eli Zaretskii
2008-08-23 19:12                 ` Bob Rogers [this message]
2008-08-23 20:51                   ` Eli Zaretskii
2008-08-23 18:05               ` Andreas Schwab
2008-08-23 18:17                 ` Eli Zaretskii
2008-08-22 11:17           ` File Owner and Group ID on Windows Eli Zaretskii
2008-08-22 11:29             ` Juanma Barranquero
2008-08-24 20:20           ` Eli Zaretskii
2008-08-24 22:52             ` Juanma Barranquero
2008-08-25  3:07               ` Eli Zaretskii
2008-08-25  3:34                 ` Lennart Borgman (gmail)
2008-08-25 12:26                 ` Juanma Barranquero
2008-08-25 12:48                   ` Lennart Borgman (gmail)
2008-08-25 12:50                     ` Juanma Barranquero
2008-08-25 12:53                       ` Lennart Borgman (gmail)
2008-08-25 15:13                         ` Juanma Barranquero

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=18608.24854.369097.535535@rgrjr.rgrjr.dyndns.org \
    --to=rogers-emacs@rgrjr.dyndns.org \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=lekktu@gmail.com \
    --cc=schwab@suse.de \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.