Thanks Jakob, These two functions work for me worked for me.
Cheers On Thursday, June 21, 2018 at 2:34:40 PM UTC-7, Jakob Kummerow wrote: > > Yes, debugging CodeStubAssembler-generated builtins is not easy. > > CodeStubAssembler provides several overloaded Print() methods for > convenient printf-style debugging. They cause code to be emitted that, at > runtime, will call some printing function. > There's also DebugBreak() inherited from CodeAssembler which will emit an > int3 instruction, which essentially acts as a breakpoint in GDB. > > On Thu, Jun 21, 2018 at 12:09 PM <[email protected] <javascript:>> > wrote: > >> Hi I'm a student trying to learn V8 and am trying to implement my own >> Array prototype method. I'm currently having difficulty debugging the >> psuedo-assembly like code and was curious if anyone had any suggestions. >> I'm currently using gdb and I'm having trouble figuring out the symbols to >> set breakpoints and adding print statements is proving to be a challenge as >> well. >> >> Sorry if this question has been asked before I searched for it and went >> back through a few months of posts and couldn't find it. >> >> Cheers, >> Jann >> >> -- >> -- >> v8-dev mailing list >> [email protected] <javascript:> >> 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] <javascript:>. >> For more options, visit https://groups.google.com/d/optout. >> > -- -- 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]. For more options, visit https://groups.google.com/d/optout.
