unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Kangas <stefan@marxist.se>
To: "Jan D." <jan.h.d@swipnet.se>
Cc: Damien Cassou <damien.cassou@gmail.com>, 9682@debbugs.gnu.org
Subject: bug#9682: Segfault from trunk with Lucid
Date: Fri, 23 Aug 2019 08:06:26 +0200	[thread overview]
Message-ID: <CADwFkmkDrqQRzDhDtrRfvYZZ5ctQcyzF8MZWmq5EVQZZY11TmA@mail.gmail.com> (raw)
In-Reply-To: <CA+y5gggxxJ_wsKuYU7Sz1X543RZPOafzgs-v0WXDpZA7=ebfUg@mail.gmail.com>

"Jan D." <jan.h.d@swipnet.se> writes:

> Damien Cassou skrev 2011-10-14 11:02:
>> On Thu, Oct 6, 2011 at 6:24 PM, Glenn Morris<rgm@gnu.org>  wrote:
>>> Looks similar to http://debbugs.gnu.org/cgi/bugreport.cgi?bug=6075
>>
>> Maybe. I can reproduce it and the bug does not seem to want to go
>> away. What can I do?
>>
>
> Compile the X libs where the crash is, or get hold of some debug info for them
> so you can see exactly what goes wrong.  There is probably some bad input, but
> what?
> It could also be a gcc issue or something debian specific.
> BTW what does -DDEBIAN enable?
>
> You can try to loose all your special CFLAGS and LDFLAGS as well as makeflags
> (-j8 has cause problems before).

Hi Damien,

That was 8 years ago.  Did you ever get a chance to look into this bug
any further?  Are you still seeing the same issue on a modern version
of Emacs, for example the latest version 26.2?

If I don't hear back from you in a couple of weeks, I'll just assume
that the issue has been fixed in the intervening years and close the
bug report.

Thanks,
Stefan Kangas





  parent reply	other threads:[~2019-08-23  6:06 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-06 11:20 bug#9682: Segfault from trunk with Lucid Damien Cassou
2011-10-06 16:24 ` Glenn Morris
2011-10-14  9:02   ` Damien Cassou
2011-10-14 13:01     ` Jan D.
2019-08-23  6:06 ` Stefan Kangas [this message]
2019-08-23  7:29   ` Damien Cassou
2019-08-23 17:19     ` Stefan Kangas

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=CADwFkmkDrqQRzDhDtrRfvYZZ5ctQcyzF8MZWmq5EVQZZY11TmA@mail.gmail.com \
    --to=stefan@marxist.se \
    --cc=9682@debbugs.gnu.org \
    --cc=damien.cassou@gmail.com \
    --cc=jan.h.d@swipnet.se \
    /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).