Displaying 9 results from an estimated 9 matches for "createpointertype".
2011 Jun 25
2
[LLVMdev] Segfault calling LLVM libs from a clang-compiled executable
...le my compiler
with clang, and link it against the llvm libs. Everything works fine up to a
point - that is, I'm able to use all of the ADT classes, derived types, and
so on - until I get into the code generation phase, at which point things
blow up. Specifically, I get a segfault in DIBuilder::createPointerType()
(well, actually the segfault is several stack levels down from that.)
Looking in gdb, it appears that there is some sort of calling convention
mismatch - my code is calling createPointerType() with an empty StringRef(),
but when I attempt to look at the StringRef argument from within the
createP...
2011 Jun 28
2
[LLVMdev] Segfault calling LLVM libs from a clang-compiled executable
...and link it against the llvm libs. Everything works fine up to a
>> point - that is, I'm able to use all of the ADT classes, derived types, and
>> so on - until I get into the code generation phase, at which point things
>> blow up. Specifically, I get a segfault in DIBuilder::createPointerType()
>> (well, actually the segfault is several stack levels down from that.)
>> Looking in gdb, it appears that there is some sort of calling convention
>> mismatch - my code is calling createPointerType() with an empty StringRef(),
>> but when I attempt to look at the StringR...
2011 Jun 25
0
[LLVMdev] Segfault calling LLVM libs from a clang-compiled executable
...with clang, and link it against the llvm libs. Everything works fine up to a
> point - that is, I'm able to use all of the ADT classes, derived types, and
> so on - until I get into the code generation phase, at which point things
> blow up. Specifically, I get a segfault in DIBuilder::createPointerType()
> (well, actually the segfault is several stack levels down from that.)
> Looking in gdb, it appears that there is some sort of calling convention
> mismatch - my code is calling createPointerType() with an empty StringRef(),
> but when I attempt to look at the StringRef argument from...
2011 Jun 30
2
[LLVMdev] Segfault calling LLVM libs from a clang-compiled executable
...orks fine up
> to a
> >>> point - that is, I'm able to use all of the ADT classes, derived types,
> and
> >>> so on - until I get into the code generation phase, at which point
> things
> >>> blow up. Specifically, I get a segfault in
> DIBuilder::createPointerType()
> >>> (well, actually the segfault is several stack levels down from that.)
> >>> Looking in gdb, it appears that there is some sort of calling
> convention
> >>> mismatch - my code is calling createPointerType() with an empty
> StringRef(),
> >>...
2011 Jun 29
0
[LLVMdev] Segfault calling LLVM libs from a clang-compiled executable
...against the llvm libs. Everything works fine up to a
>>> point - that is, I'm able to use all of the ADT classes, derived types, and
>>> so on - until I get into the code generation phase, at which point things
>>> blow up. Specifically, I get a segfault in DIBuilder::createPointerType()
>>> (well, actually the segfault is several stack levels down from that.)
>>> Looking in gdb, it appears that there is some sort of calling convention
>>> mismatch - my code is calling createPointerType() with an empty StringRef(),
>>> but when I attempt to loo...
2011 Jul 24
3
[LLVMdev] Segfault calling LLVM libs from a clang-compiled executable
.... Now I am getting the
> same error that I was getting previously.
> Is it possible that your fix got unfixed when they merged in the new branch?
I wouldn't be surprised if something broke, but I would be surprised
if it's exactly the same issue. It's crashing calling
DIBuilder::createPointerType again?
-Eli
2011 Jul 24
0
[LLVMdev] Segfault calling LLVM libs from a clang-compiled executable
...gt;> >>> point - that is, I'm able to use all of the ADT classes, derived
>> types, and
>> >>> so on - until I get into the code generation phase, at which point
>> things
>> >>> blow up. Specifically, I get a segfault in
>> DIBuilder::createPointerType()
>> >>> (well, actually the segfault is several stack levels down from that.)
>> >>> Looking in gdb, it appears that there is some sort of calling
>> convention
>> >>> mismatch - my code is calling createPointerType() with an empty
>> String...
2011 Aug 18
0
[LLVMdev] Segfault calling LLVM libs from a clang-compiled executable
...> same error that I was getting previously.
>> Is it possible that your fix got unfixed when they merged in the new branch?
>
> I wouldn't be surprised if something broke, but I would be surprised
> if it's exactly the same issue. It's crashing calling
> DIBuilder::createPointerType again?
Did you ever make any progress narrowing this down?
-Eli
2011 Apr 30
0
[LLVMdev] Compiling my LLVM-based project using clang
I've recently been attempting to use clang to build my llvm-based frontend
and I'm having some problems. I finally got everything to compile, but I'm
getting a strange segfault in DIBuilder when I try to run.
The crash occurs inside DIBuilder::createPointerType(). The fourth parameter
to this function is a StringRef, whose default value is an empty string.
Since I'm not supplying a value for this parameter, what I would expect to
see in the debugger is a StringRef whose data and length are both 0. But
what I see in gdb is this:
$5 = {Data = 0x0, L...