unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "andrés ramírez" <rrandresf@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 38133@debbugs.gnu.org
Subject: bug#38133: 27.0.50; compiling master and core dump with r139382-1
Date: Fri, 08 Nov 2019 17:23:54 +0000	[thread overview]
Message-ID: <86eeyiwac5.fsf@gmail.com> (raw)
In-Reply-To: <83eeyib8js.fsf@gnu.org>

Hi Eli. SOLVED.

When You pointed out LDFLAGS, that gave me some hints. About similar
problems in the past (i have read on emacs-devel). Most of them were solved with 'make bootstrap'. So
I modified my packaging script for also including {./autogen.sh; make
bootstrap}. This solved It.

>> Thread 1 "emacs" received signal SIGSEGV, Segmentation fault.
>> 0x006283d5 in xlw_create_menubar (instance=0xd122f0) at
>> lwlib-Xlw.c:139 139 XtSetArg (al[ac], XtNmenu,
>> instance->info->val); ac++;

Eli> OK, so which of these caused the crash?  Is one of them a NULL
Eli> pointer or an invalid pointer, or is ac a garbled value?

Probably this is going to be irrelevant. But as the debugging session
was still open:
--8<---------------cut here---------------start------------->8---
Thread 1 "emacs" received signal SIGSEGV, Segmentation fault.
0x006283d5 in xlw_create_menubar (instance=0xd12520) at lwlib-Xlw.c:139
139	  XtSetArg (al[ac], XtNmenu, instance->info->val); ac++;
(gdb) p al
$1 = {{name = 0x6337dc "menu", value = -1236906428}, {name = 0xb633fb60 <malloc+400> "\211Dž\300\017\204", <incomplete sequence \306>, value = 13594960}, {name = 0xc7b1c0 "", value = 3}, {name = 0x709d2c "\254\232\060", value = 13594960}, {name = 0xc7b1c0 "", value = 3}}
(gdb) p al[ac]
$2 = {name = 0x6337dc "menu", value = -1236906428}
(gdb) p ac
$3 = 0
(gdb) p XtNmenu
$4 = "menu"
(gdb) p instance->info->val
Cannot access memory at address 0xc
(gdb)
--8<---------------cut here---------------end--------------->8---

AR.
ps: should I close de bug report?





  reply	other threads:[~2019-11-08 17:23 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-08 13:53 bug#38133: 27.0.50; compiling master and core dump with r139382-1 rrandresf
2019-11-08 14:36 ` Eli Zaretskii
2019-11-08 14:44   ` andrés ramírez
2019-11-08 15:21     ` Eli Zaretskii
2019-11-08 15:43       ` andrés ramírez
2019-11-08 16:11         ` Eli Zaretskii
2019-11-08 16:40           ` andrés ramírez
2019-11-08 17:08             ` Eli Zaretskii
2019-11-08 17:23               ` andrés ramírez [this message]
2019-11-08 19:08                 ` Eli Zaretskii
2019-11-08 19:27                   ` bug#38133: close 38133 andrés ramírez
2019-11-08 23:25 ` bug#38133: 27.0.50; compiling master and core dump with r139382-1 Paul Eggert

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=86eeyiwac5.fsf@gmail.com \
    --to=rrandresf@gmail.com \
    --cc=38133@debbugs.gnu.org \
    --cc=eliz@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).