I can see two approaches of writing a test for the bug: 1) generate code such that its safepoint table is faulty and then manually inspect its safepoint table, or 2) generate code such that its safepoint table is faulty and running it will trigger a GC or deopt at the problematic pc, and run this code. (1) will probably require you to expose some internals for testing. We can discuss details in the code review tool.
Best, Georg -- -- v8-dev mailing list [email protected] http://groups.google.com/group/v8-dev --- You received this message because you are subscribed to the Google Groups "v8-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/v8-dev/CABT__oFDwPakYTuz5_tYWY8R4or%3D1k%2BnpPvs9fzOt72CnyF9Bw%40mail.gmail.com.
