Bugs item #2938842, was opened at 2010-01-24 21:21
Message generated for change (Tracker Item Submitted) made by sjoerd
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=482468&aid=2938842&group_id=56967

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: SQL/Core
Group: MonetDB5 CVS Head
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Sjoerd Mullender (sjoerd)
Assigned to: Niels Nes (nielsnes)
Summary: second dump causes crash

Initial Comment:
Using a database created with the HEAD version of 2009-12-02, but running with 
a server checked out from HEAD on 2010-01-24, the second consecutive dump 
(running msqldump) causes a segfault at
    at /home/sjoerd/src/MonetDB/devel/MonetDB/src/gdk/gdk_bbp.mx:1830
1830            assert(BBP_cache(i)->batSharecnt >= 0);

The reason for the segfault is
(gdb) p BBP[i]
$1 = {b = {0x0, 0x0}, nme = {0x615288 "tmp_141", 0x6152a8 "tmpr_141"}, bak = {
    0x0, 0x0}, next = {0, 0}, cache = 0x6150b8, path = 0x6152d8 "01/141", 
  refs = 0, lrefs = 4, lastused = 32996, status = 32}

(This is a new report based on a comment in #2935207 which was for a different 
bug.)

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=482468&aid=2938842&group_id=56967

------------------------------------------------------------------------------
Throughout its 18-year history, RSA Conference consistently attracts the
world's best and brightest in the field, creating opportunities for Conference
attendees to learn about information security's most important issues through
interactions with peers, luminaries and emerging and established companies.
http://p.sf.net/sfu/rsaconf-dev2dev
_______________________________________________
Monetdb-bugs mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/monetdb-bugs

Reply via email to