* bug#14221: 24.2 or 24.1; fatal_error_signal: Process /usr/bin/emacs-24.[1|2] was killed by signal 11 (SIGSEGV)
@ 2013-04-17 8:21 Petr Hracek
2013-04-19 23:24 ` Glenn Morris
0 siblings, 1 reply; 6+ messages in thread
From: Petr Hracek @ 2013-04-17 8:21 UTC (permalink / raw)
To: 14221
Hi folks,
I have just a question related to emacs-24.[1|2] versions.
Sometimes as on my PC as from BZ reports
https://bugzilla.redhat.com/show_bug.cgi?id=861084
https://bugzilla.redhat.com/show_bug.cgi?id=878455
https://bugzilla.redhat.com/show_bug.cgi?id=895751
https://bugzilla.redhat.com/show_bug.cgi?id=908649
emacs crashed with SIGSEGV.
Each BZ reports have the same text like:
[abrt] emacs-24.[1|2]-[version].fc[17|18]: fatal_error_signal: Process
/usr/bin/emacs-24.[1|2] was killed by signal 11 (SIGSEGV)
Do you know what causes that problems?
Are these problems known?
I tried to find out any patches related to that problem but without success.
I think that it is related to issues that emacs is started as server/deamon
but I am not sure for that.
--
S pozdravem / Best regards
Petr Hracek
^ permalink raw reply [flat|nested] 6+ messages in thread
* bug#14221: 24.2 or 24.1; fatal_error_signal: Process /usr/bin/emacs-24.[1|2] was killed by signal 11 (SIGSEGV)
2013-04-17 8:21 bug#14221: 24.2 or 24.1; fatal_error_signal: Process /usr/bin/emacs-24.[1|2] was killed by signal 11 (SIGSEGV) Petr Hracek
@ 2013-04-19 23:24 ` Glenn Morris
2013-05-14 11:31 ` Petr Hracek
0 siblings, 1 reply; 6+ messages in thread
From: Glenn Morris @ 2013-04-19 23:24 UTC (permalink / raw)
To: 14221
Petr Hracek wrote:
> https://bugzilla.redhat.com/show_bug.cgi?id=861084
> https://bugzilla.redhat.com/show_bug.cgi?id=878455
> https://bugzilla.redhat.com/show_bug.cgi?id=895751
> https://bugzilla.redhat.com/show_bug.cgi?id=908649
There are some backtraces there if anyone wants to take a look.
The most helpful thing with crashes would be a backtrace from an Emacs
24.3 built without optimization. If there is such, please send it here.
^ permalink raw reply [flat|nested] 6+ messages in thread
* bug#14221: 24.2 or 24.1; fatal_error_signal: Process /usr/bin/emacs-24.[1|2] was killed by signal 11 (SIGSEGV)
2013-04-19 23:24 ` Glenn Morris
@ 2013-05-14 11:31 ` Petr Hracek
2013-05-14 15:57 ` Glenn Morris
0 siblings, 1 reply; 6+ messages in thread
From: Petr Hracek @ 2013-05-14 11:31 UTC (permalink / raw)
To: Glenn Morris; +Cc: 14221
emacs is build up with:
%configure --with-dubs --with-gif --with-jpeg --with-png
--with-x-toolkit=gtk3
How to change compilation for huge traces?
On 04/20/2013 01:24 AM, Glenn Morris wrote:
> Petr Hracek wrote:
>
>> https://bugzilla.redhat.com/show_bug.cgi?id=861084
>> https://bugzilla.redhat.com/show_bug.cgi?id=878455
>> https://bugzilla.redhat.com/show_bug.cgi?id=895751
>> https://bugzilla.redhat.com/show_bug.cgi?id=908649
> There are some backtraces there if anyone wants to take a look.
>
> The most helpful thing with crashes would be a backtrace from an Emacs
> 24.3 built without optimization. If there is such, please send it here.
--
Best regards / S pozdravem
Petr Hracek
^ permalink raw reply [flat|nested] 6+ messages in thread
* bug#14221: 24.2 or 24.1; fatal_error_signal: Process /usr/bin/emacs-24.[1|2] was killed by signal 11 (SIGSEGV)
2013-05-14 11:31 ` Petr Hracek
@ 2013-05-14 15:57 ` Glenn Morris
2013-05-14 17:14 ` Glenn Morris
2015-12-25 23:26 ` Lars Ingebrigtsen
0 siblings, 2 replies; 6+ messages in thread
From: Glenn Morris @ 2013-05-14 15:57 UTC (permalink / raw)
To: Petr Hracek; +Cc: 14221
Petr Hracek wrote:
> emacs is build up with:
> %configure --with-dubs --with-gif --with-jpeg --with-png
> --with-x-toolkit=gtk3
>
> How to change compilation for huge traces?
Something like:
CFLAGS="-O0 -g3" configure ...
^ permalink raw reply [flat|nested] 6+ messages in thread
* bug#14221: 24.2 or 24.1; fatal_error_signal: Process /usr/bin/emacs-24.[1|2] was killed by signal 11 (SIGSEGV)
2013-05-14 15:57 ` Glenn Morris
@ 2013-05-14 17:14 ` Glenn Morris
2015-12-25 23:26 ` Lars Ingebrigtsen
1 sibling, 0 replies; 6+ messages in thread
From: Glenn Morris @ 2013-05-14 17:14 UTC (permalink / raw)
To: Petr Hracek; +Cc: 14221
Glenn Morris wrote:
> Something like:
>
> CFLAGS="-O0 -g3" configure ...
PS It is also good to then run Emacs from its src/ directory, so it
picks up its .gdbinit (you may need to set gdb's auto-load safe-path).
Then do `backtrace full' when it crashes.
^ permalink raw reply [flat|nested] 6+ messages in thread
* bug#14221: 24.2 or 24.1; fatal_error_signal: Process /usr/bin/emacs-24.[1|2] was killed by signal 11 (SIGSEGV)
2013-05-14 15:57 ` Glenn Morris
2013-05-14 17:14 ` Glenn Morris
@ 2015-12-25 23:26 ` Lars Ingebrigtsen
1 sibling, 0 replies; 6+ messages in thread
From: Lars Ingebrigtsen @ 2015-12-25 23:26 UTC (permalink / raw)
To: Glenn Morris; +Cc: 14221
Glenn Morris <rgm@gnu.org> writes:
> Petr Hracek wrote:
>
>> emacs is build up with:
>> %configure --with-dubs --with-gif --with-jpeg --with-png
>> --with-x-toolkit=gtk3
>>
>> How to change compilation for huge traces?
>
> Something like:
>
> CFLAGS="-O0 -g3" configure ...
More information was requested, but no response was given within a few
months, so I'm closing this bug report. If the problem still exists,
please reopen this bug report.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2015-12-25 23:26 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2013-04-17 8:21 bug#14221: 24.2 or 24.1; fatal_error_signal: Process /usr/bin/emacs-24.[1|2] was killed by signal 11 (SIGSEGV) Petr Hracek
2013-04-19 23:24 ` Glenn Morris
2013-05-14 11:31 ` Petr Hracek
2013-05-14 15:57 ` Glenn Morris
2013-05-14 17:14 ` Glenn Morris
2015-12-25 23:26 ` Lars Ingebrigtsen
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).