🚀 go-pugleaf

I have the following problems, does anyone have any solutions?

The systems in mind are System V Rel 4, SPARC using C and/or C++.

1. How do software vendors analyse cores produced by their software on
   a customer's machine when the software in question has been
   optimised?

    In trying to solve 1. above, I tried using both -g and -O with gcc.
    The plan was to give the customer -O code only (possibly stripped)
    and when a core was produced to debug it using a source level debugger
    with -g -O compiled code.
    This method seemed to find the right source line, but I could not get
    at any local variables by name, although I guess the information may
    have been there on the stack somewhere.

    Can anyone suggest any alternatives?

    Does anyone with gcc knowledge know which (if any) of the
    optimisations I should avoid to increase my chances of using a source
    level debugger "normally"?

2. Does anyone have any code to help apply software patches to code?

--
        John M Kewley
 
ICL Computers Limited, Wenlock Way, West Gorton, Manchester. M12 5DR
Tel: (+44) 61 223 1301 X2138  Email: jk@fiveg.icl.co.uk or jk@cs.man.ac.uk