Bug report: crash when close blob handle after close_v2 db

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

Bug report: crash when close blob handle after close_v2 db

Chaoji Li
This problem is only present for 3.28+. A sample test case is attached.

Basically, the flow is:

1. Open  in-memory db A (we don't do anything about it).
2. Open db B  from file test.db
3. Create a blob handle from B
4. close_v2 A
5. close_v2 B
6. close blob handle -> Segmentation fault

The problem seems to go away if A is not created.
_______________________________________________
sqlite-users mailing list
[hidden email]
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
Reply | Threaded
Open this post in threaded view
|

Re: Bug report: crash when close blob handle after close_v2 db

Simon Slavin-3
On 14 Jul 2019, at 11:18am, Chaoji Li <[hidden email]> wrote:

> This problem is only present for 3.28+. A sample test case is attached.

Thank you for identifying this behaviour.  I'm sure the development team will reply to your post.

Attachments are automatically ignored by the mailing list.  You can include your code in your message, or post it on a server and include a pointer.  However, in this case you have included a good clear description of how to reproduce the problem and this should not be necessary.
_______________________________________________
sqlite-users mailing list
[hidden email]
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
Reply | Threaded
Open this post in threaded view
|

Re: Bug report: crash when close blob handle after close_v2 db

Dan Kennedy-4
In reply to this post by Chaoji Li

On 14/7/62 17:18, Chaoji Li wrote:
> This problem is only present for 3.28+. A sample test case is attached.

Thanks for reporting this. We think it's fixed here:

   https://sqlite.org/src/info/52f463d29407fad6

The mailing list stripped off your test case, so if you could either run
it with the latest SQLite from fossil or else post it inline here so
that we can run it, that would be very helpful.

Thanks,

Dan.



>
> Basically, the flow is:
>
> 1. Open  in-memory db A (we don't do anything about it).
> 2. Open db B  from file test.db
> 3. Create a blob handle from B
> 4. close_v2 A
> 5. close_v2 B
> 6. close blob handle -> Segmentation fault
>
> The problem seems to go away if A is not created.
> _______________________________________________
> sqlite-users mailing list
> [hidden email]
> http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
_______________________________________________
sqlite-users mailing list
[hidden email]
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users