bugDDD - Bugs: bug #24842, DDD 3.3.11 (sparc-sun-solaris2.9)...


bug #24842: DDD 3.3.11 (sparc-sun-solaris2.9) gets `Bus Error' signal

Submitter:  None
Submitted:  Sat 15 Nov 2008 12:23:31 AM UTC
Category:  None Severity:  3 - Normal
Item Group:  None Status:  Need Info
Privacy:  Public Assigned to:  pwainwright
Open/Closed:  Open Release:  None
* Mandatory Fields

Add a New Comment (Rich Markup)

Comment Type & Canned Response:
       No canned response available


( Jump to the original submission )

Mon 17 Nov 2008 07:10:41 PM UTC, comment #7: 

Compiling ddd-3.3.11 with gcc-3.2.3 did not solve the problem.


Jay St. Pierre <stpierre>
Mon 17 Nov 2008 03:57:47 PM UTC, comment #6: 

It appears valgrind is not available for sparc-solaris-2.9.  We do have access to purify, but I have no idea how to run it.

I do not get the error on sparc-solaris-2.10 or mips-IRIX64-6.5.

Perhaps I will try compiling ddd with an older version of gcc.


Jay St. Pierre <stpierre>
Sun 16 Nov 2008 05:41:40 PM UTC, comment #5: 

It looks like the bug is probably caused by corruption of the data structures used by the emutls routines.

The only way forward would seem to be to run the program under valgrind --tool=memcheck, or some equivalent.

Peter Wainwright <pwainwright>
Sun 16 Nov 2008 10:43:26 AM UTC, comment #4: 

I fear this may be a difficult error to track down.

The bus error seems to occur in emutls_destroy, which is called from exit() after the program itself has finished.  As far as I know, the emutls stuff is part of libgcc, and was added to support system which do not have native TLS (thread-local storage).

As I don't have a Solaris system, and my GNU/Linux systems do not use emutls at all (it uses pthread_getspecific etc.), I'm not able to reproduce the bug.

The good news is that since the bus error occurs after the call to exit(), DDD has already finished its work.  The improper exit is ugly, and leaves core dumps all over your system, but it shouldn't affect the operation of DDD.

Peter Wainwright <pwainwright>
Sun 16 Nov 2008 03:47:21 AM UTC, comment #3: 

I built and installed ddd-3.3.10 with the same results.  ddd-3.3.8, the version we had previously installed, would not compile with gcc-4.3.2.


Jay St. Pierre <stpierre>
Sat 15 Nov 2008 07:14:30 PM UTC, comment #2: 

I have attached a stack trace.


(file #16848)

Jay St. Pierre <stpierre>
Sat 15 Nov 2008 09:39:18 AM UTC, comment #1: 

Can you get a stack trace?

The error message indicated that a core dump was generated (this would probably be called something like "core" or "core.12345").

If you can, please load this into gdb and print out the stack, thus:

$ gdb ddd core
(gdb) info stack
(gdb) quit

and attach the results (...) to this bug report.  If ddd was not compiled with debugging flags, the trace might be impossible to interpret (no source filenames or line numbers): in that case please try to recompile with CFLAGS=-g and CXXFLAGS=-g and reproduce the bug.

Of course, it would be more sensible if DDD would dump its own stack automatically: sounds like a good idea for the next version...

Peter Wainwright <pwainwright>
Sat 15 Nov 2008 12:23:31 AM UTC, original submission:  

I just built and installed ddd-3.3.11.  When I do a test run by simply starting the program and then doing either a "quit" at the gdb prompt or terminating the program with the pull down menus I get a core dump.  I'm not even trying to debug with it yet.  The console output is:

Creating "/home/stpierre/.ddd/"...
Creating "/home/stpierre/.ddd/"...done.
Creating "/home/stpierre/.ddd/sessions/"...
Creating "/home/stpierre/.ddd/sessions/"...done.
Creating "/home/stpierre/.ddd/themes/"...
Creating "/home/stpierre/.ddd/themes/"...done.

warning: Can't read pathname for load map: I/O error.

warning: Can't read pathname for load map: I/O error.

warning: Can't read pathname for load map: I/O error.

Internal error (Bus Error).

Oops!  You have found a bug in DDD.

If you can reproduce this bug, please send a bug report
to <ddd@gnu.org>, giving a subject like

    DDD 3.3.11 (sparc-sun-solaris2.9) gets `Bus Error' signal

To enable us to fix the bug, you should include the following information:

  • What you were doing to get this message.  Report all the facts.
  • The contents of the `~/.ddd/log' file as generated by this session.

Please read also the section "Reporting Bugs" in the DDD manual.

We thank you for your support.

Bus Error (core dumped)



(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach Files:

Attached Files
file #16848:  ddd_stack_trace.txt added by stpierre (1KiB - text/plain)
file #16844:  log added by None (11KiB - application/octet-stream)


Depends on the following items: None found

Items that depend on this one: None found


Carbon-Copy List
  • -email is unavailable- added by stpierre (Updated the item)
  • -email is unavailable- added by pwainwright (Posted a comment)

    There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

    Only logged-in users can vote.





    Follow 4 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2008-11-15 pwainwright Assigned toNone pwainwright
    2008-11-15 stpierre Attached File- Added ddd_stack_trace.txt, #16848
    2008-11-15 pwainwright StatusNone Need Info
    2008-11-15 None Attached File- Added log, #16844

    Back to the top

    Powered by Savane 3.9