Skip to content

unary primitive type (101) cause SIGSEGV (Segmentation fault) when query result is processed in c library #30

Open
@tojocky

Description

Hi,

I found that if a query from a table where a value has unary primite type (101) then c library (c.o) ends up in Segmentation fault.

How to reproduce:
create a table with a column type Char (10).
insert some data where a row should contain unary primitive type (101)

create a simple C/C++ that execute the query.

I tried with the latest client version c.0 v.4.0 and it still coring. Unfortunately I cannot paste any code here.

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions