[ET Trac] [Einstein Toolkit] #1100: Correct backtrace generation in Carpet

Einstein Toolkit trac-noreply at einsteintoolkit.org
Fri Aug 16 17:55:01 CDT 2013


#1100: Correct backtrace generation in Carpet
-----------------------+----------------------------------------------------
  Reporter:  eschnett  |       Owner:  eschnett
      Type:  defect    |      Status:  new     
  Priority:  major     |   Milestone:          
 Component:  Carpet    |     Version:          
Resolution:            |    Keywords:          
-----------------------+----------------------------------------------------

Comment (by rhaas):

 Replying to [comment:1 hinder]:
 > Given that backtraces are very useful, and used to work on "standard"
 linux systems, maybe the code could be enabled despite the problems that
 you mention.  The memory allocation errors and buffers shouldn't be a
 problem since this only happens when the process is about to terminate due
 to the error anyway, right?  Can we detect that we have glibc and Linux,
 and enable the backtrace code in that case?  I know it's not as elegant as
 correctly autoconfing everything, but it's probably a lot easier.  And
 having a backtrace with meaningful symbols is extremely useful.

 I second that :-)

-- 
Ticket URL: <https://trac.einsteintoolkit.org/ticket/1100#comment:2>
Einstein Toolkit <http://einsteintoolkit.org>
The Einstein Toolkit


More information about the Trac mailing list