On Fri, Apr 26, 2013 at 4:39 AM, Amy <[email protected]> wrote: > I got the following errors when I was trying to compile with "gdbjit=on", > how to solve it? > > CXX(target) /workspace/v8/out/native/obj.target/v8_base/src/gdb-jit.o > ../src/gdb-jit.cc:503:13: error: no matching constructor for initialization > of > 'ZoneList<v8::internal::MachOSection *>' > MachO() : sections_(6) { } > ^ ~ > ../src/zone.h:183:7: note: candidate constructor (the implicit copy > constructor) not viable: no > known conversion from 'int' to 'const > v8::internal::ZoneList<v8::internal::MachOSection *>' > for 1st argument; > class ZoneList: public List<T, ZoneAllocationPolicy> { > ^ > ../src/zone.h:187:3: note: candidate constructor not viable: requires 2 > arguments, but 1 was > provided > ZoneList(int capacity, Zone* zone) > ^ > ../src/zone.h:193:3: note: candidate constructor not viable: requires 2 > arguments, but 1 was > provided > ZoneList(const ZoneList<T>& other, Zone* zone) > ^ > ../src/gdb-jit.cc:506:26: error: too few arguments to function call, > expected 2, have 1 > sections_.Add(section); > ~~~~~~~~~~~~~ ^ > ../src/zone.h:201:3: note: 'Add' declared here > INLINE(void Add(const T& element, Zone* zone)) { > ^ > ../src/globals.h:326:24: note: expanded from macro 'INLINE' > #define INLINE(header) inline header __attribute__((always_inline)) > ^ > ../src/gdb-jit.cc:1795:55: error: too many arguments to function call, > expected 1, have 2 > obj->AddSection(new(zone) DebugInfoSection(desc), zone); > ~~~~~~~~~~~~~~~ ^~~~ > ../src/gdb-jit.cc:505:3: note: 'AddSection' declared here > uint32_t AddSection(MachOSection* section) { > ^ > ../src/gdb-jit.cc:1796:57: error: too many arguments to function call, > expected 1, have 2 > obj->AddSection(new(zone) DebugAbbrevSection(desc), zone); > ~~~~~~~~~~~~~~~ ^~~~ > ../src/gdb-jit.cc:505:3: note: 'AddSection' declared here > uint32_t AddSection(MachOSection* section) { > ^ > ../src/gdb-jit.cc:1797:55: error: too many arguments to function call, > expected 1, have 2 > obj->AddSection(new(zone) DebugLineSection(desc), zone); > ~~~~~~~~~~~~~~~ ^~~~ > ../src/gdb-jit.cc:505:3: note: 'AddSection' declared here > uint32_t AddSection(MachOSection* section) { > ^ > ../src/gdb-jit.cc:1800:54: error: too many arguments to function call, > expected 1, have 2 > obj->AddSection(new(zone) UnwindInfoSection(desc), zone); > ~~~~~~~~~~~~~~~ ^~~~ > ../src/gdb-jit.cc:505:3: note: 'AddSection' declared here > uint32_t AddSection(MachOSection* section) { > ^ > ../src/gdb-jit.cc:1925:21: error: no matching function for call to 'operator > new' > mach_o.AddSection(new MachOTextSection(kCodeAlignment, > ^ > ../src/zone-inl.h:97:19: note: candidate function not viable: requires 2 > arguments, but 1 was > provided > void* ZoneObject::operator new(size_t size, Zone* zone) { > ^ > 7 errors generated.
I assume that's with the HEAD of trunk? I don't think anyone really maintains the gdbjit interface. You'll either have to patch it yourself (and do send the patch upstream) or downgrade to an older release. -- -- v8-users mailing list [email protected] http://groups.google.com/group/v8-users --- You received this message because you are subscribed to the Google Groups "v8-users" 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/groups/opt_out.
