Saving stack trace in java for any object at the time of it's creation and using it at any other point in the program

For debugging purpose, I want to save the stack trace when an object was created and refer/print it at a later point in the program. I tried adding a field to Object class in OpenJDK itself but as mentioned in here it will cause a problem with hard coded elements in OpenJDK.

Can someone please suggest an efficient way to do this.

If the object is large, or frequent, JFR will sample the allocation. By default it samples up to 150 times/s.

JDK 16, or later:

$ java -XX:StartFlightRecording:filename=exitdump.jfr MyApp
...
Stop the application
$ jfr print --events ObjectAllocationSample --stack-depth 64 exitdump.jfr

jdk.ObjectAllocationSample {
  startTime = 12:00:19.826
  objectClass = byte[] (classLoader = bootstrap)
  weight = 23.1 kB
  eventThread = "Image Animator 0" (javaThreadId = 33)
  stackTrace = [
    sun.awt.image.GifFrame.dispose() line: 723
    sun.awt.image.GifImageDecoder.produceImage() line: 247
    sun.awt.image.InputStreamImageSource.doFetch() line: 269
    sun.awt.image.ImageFetcher.fetchloop() line: 212
    sun.awt.image.ImageFetcher.run() line: 176
  ]
}
...

If it's your code, you can simply construct an Exception at the time of constructing the object:

public class MyObject {
   public final Exception creationPoint = new Exception();

   ...
}

Then, creationPoint.printStackTrace() will print the creation point (or you can call getStackTrace() to query it programmatically). As GhostCat points out, collecting the stack trace (which happens on construction of the Exception object) of course has a performance hit, so you would generally use this technique judiciously to investigate a specific issue with objects that are generated relatively infrequently.

Collecting a stack trace for any object, and storing that information with the object that simply isn't possible in an efficient manner.

Collecting stack trace information is expensive, and there is no way to do that "on scale", as part of normal program execution. Keep in mind that the primary purpose of stack traces is to collect that information after an exception occurred.

Beyond that, it is also conceptually wrong. If you only talk about very few specific objects, then the appropriate approach would be to carefully study the paths in your code that create these objects, and maybe have the code that creates objects do extensive logging. But if you really talk about many different sort of objects, then your request rather implies that the overall logging concept in your code is insufficient. Focus on that part then.

JFR may be what you need, the tool can capture stack information when an object is created, but it seems to capture only part of the all objects.