Bug 663253 - Optionally run erlexec in gdb?
Summary: Optionally run erlexec in gdb?
Alias: None
Product: Fedora
Classification: Fedora
Component: erlang
Version: rawhide
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
Assignee: Peter Lemenkov
QA Contact: Fedora Extras Quality Assurance
URL: http://blog.dizzyd.com/blog/2009/12/1...
Depends On:
TreeView+ depends on / blocked
Reported: 2010-12-15 06:50 UTC by Hans Ulrich Niedermann
Modified: 2016-01-27 15:16 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Last Closed: 2015-02-17 13:32:24 UTC
Type: ---

Attachments (Terms of Use)

Description Hans Ulrich Niedermann 2010-12-15 06:50:29 UTC
Description of problem:

   An option to run erlang in gdb similar to
   http://dizzyd.com/blog/post/190 could be
   quite useful.

   The solution in dizzyd's blog uses setting USE_GDB to
   a non-empty string to make erlexec run in gdb. There
   might be a better suited environment variable and value.

   A command line parameter (--debug -g) as used in /usr/bin/firefox
   does not look advisable due to erl's peculiar way of parsing command
   line options, and other params not fitting in well with that.

   Perhaps this should be taken to upstream first, though.

   Running gdb on erlexec is useful because e.g. using wx in some
   constellations reproducibly segfaults beam.smp.

Version-Release number of selected component (if applicable):

   R14B-0.15.fc14 (and all other versions, to be exact)

How reproducible:


Steps to Reproduce:

Actual results:

   No easy way to run erl in gdb.

Expected results:

   Easy way to run erl in gdb.

Additional info:

   This is mostly a reminder of this issue to myself.

Comment 1 Fedora End Of Life 2013-04-03 18:44:56 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle.
Changing version to '19'.

(As we did not run this process for some time, it could affect also pre-Fedora 19 development
cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.)

More information and reason for this action is here:

Comment 2 Fedora End Of Life 2015-01-09 16:29:04 UTC
This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 19 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 3 Fedora End Of Life 2015-02-17 13:32:24 UTC
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this

Thank you for reporting this bug and we are sorry it could not be fixed.

Note You need to log in before you can comment on or make changes to this bug.