Sigil-0.8.900 released for testing - Wait for Sigil-0.8.901

[KevinH]

Hi DiapDealer,
You might want to try updating to the latest VS C++ Redistributables for VS 2010 on that old vista machine to see if it helps or not. I also think there is an old VS debugger you can run to at least get some sort of backtrace. I will look to see if I can find it on my Windows VM.
KevinH

[DiapDealer]

It's sigilgumbo.dll that's faulting. Check your email Kevin.

@Pete6055. If you could verify that it's the same faulting module on Windows 7 (sigilgumbo.dll), by checking the Windows event log after it crashes, that would be great.

[theducks]

W10 x64
TOC from Headers crashes
Split file crashes

[DiapDealer]

Originally Posted by theducks

W10 x64
TOC from Headers crashes
Split file crashes

Can you get us some Event viewer entries from the crashes, please?

[pete6055]

Originally Posted by DiapDealer

It's sigilgumbo.dll that's faulting. Check your email Kevin.

@Pete6055. If you could verify that it's the same faulting module on Windows 7 (sigilgumbo.dll), by checking the Windows event log after it crashes, that would be great.

Confirmed on Vista; log attached. No doubt, sigilgumbo.dll would also be the problem on Win7

[theducks]

Originally Posted by DiapDealer

Can you get us some Event viewer entries from the crashes, please?

Here you go. More Gumbo

Spoiler:

Log Name: Application
Source: Application Error
Date: 24-Sep-15 17:21:26
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: Centaur
Description:
Faulting application name: Sigil.exe, version: 0.8.900.0, time stamp: 0x5603629f
Faulting module name: sigilgumbo.dll, version: 0.0.0.0, time stamp: 0x56036144
Exception code: 0xc0000005
Fault offset: 0x0000000000001097
Faulting process id: 0x1a6c
Faulting application start time: 0x01d0f72811a70491
Faulting application path: C:\Program Files\Sigil\Sigil.exe
Faulting module path: C:\Program Files\Sigil\sigilgumbo.dll
Report Id: 282c2983-e73b-4723-98a2-c198ee9fbd76
Faulting package full name:
Faulting package-relative application ID:
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Level>2</Level>
<Task>100</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2015-09-25T00:21:26.000000000Z" />
<EventRecordID>2598</EventRecordID>
<Channel>Application</Channel>
<Computer>Centaur</Computer>
<Security />
</System>
<EventData>
<Data>Sigil.exe</Data>
<Data>0.8.900.0</Data>
<Data>5603629f</Data>
<Data>sigilgumbo.dll</Data>
<Data>0.0.0.0</Data>
<Data>56036144</Data>
<Data>c0000005</Data>
<Data>0000000000001097</Data>
<Data>1a6c</Data>
<Data>01d0f72811a70491</Data>
<Data>C:\Program Files\Sigil\Sigil.exe</Data>
<Data>C:\Program Files\Sigil\sigilgumbo.dll</Data>
<Data>282c2983-e73b-4723-98a2-c198ee9fbd76</Data>
<Data>
</Data>
<Data>
</Data>
</EventData>
</Event>

[DiapDealer]

Originally Posted by theducks

Here you go. More Gumbo

Spoiler:

Log Name: Application
Source: Application Error
Date: 24-Sep-15 17:21:26
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: Centaur
Description:
Faulting application name: Sigil.exe, version: 0.8.900.0, time stamp: 0x5603629f
Faulting module name: sigilgumbo.dll, version: 0.0.0.0, time stamp: 0x56036144
Exception code: 0xc0000005
Fault offset: 0x0000000000001097
Faulting process id: 0x1a6c
Faulting application start time: 0x01d0f72811a70491
Faulting application path: C:\Program Files\Sigil\Sigil.exe
Faulting module path: C:\Program Files\Sigil\sigilgumbo.dll
Report Id: 282c2983-e73b-4723-98a2-c198ee9fbd76
Faulting package full name:
Faulting package-relative application ID:
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Level>2</Level>
<Task>100</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2015-09-25T00:21:26.000000000Z" />
<EventRecordID>2598</EventRecordID>
<Channel>Application</Channel>
<Computer>Centaur</Computer>
<Security />
</System>
<EventData>
<Data>Sigil.exe</Data>
<Data>0.8.900.0</Data>
<Data>5603629f</Data>
<Data>sigilgumbo.dll</Data>
<Data>0.0.0.0</Data>
<Data>56036144</Data>
<Data>c0000005</Data>
<Data>0000000000001097</Data>
<Data>1a6c</Data>
<Data>01d0f72811a70491</Data>
<Data>C:\Program Files\Sigil\Sigil.exe</Data>
<Data>C:\Program Files\Sigil\sigilgumbo.dll</Data>
<Data>282c2983-e73b-4723-98a2-c198ee9fbd76</Data>
<Data>
</Data>
<Data>
</Data>
</EventData>
</Event>

Cool. Thanks!

[KevinH]

Hi,
I think I have a possible fix for this error. It may be happening only on Windows because of how QString toUtf8() returns a QByteArray whose address is actually a pointer to the utf8 string of characters on Linux and Mac but not on Windows. So instead I should be using toUtf8().constData() to get a proper pointer for all platforms.

Each time I took that incorrect shortcut it was in the gumbo_attribute_set_value and other gumbo routines which maps exactly to the symbol table of where the segfaults are happening.

I have pushed the fix and hopefully tomorrow after work DiapDealer will be able to tell us if it was successful.

Thanks for your bug reports. Until we get this nailed down please don't use Windows Sigil-0.8.900 for any type of production "just to be safe".

Thanks!

Kevin

[Toxaris]

Wow guys, great work! It is always hard to make such changes under the hood. And your bugfixing speed is great as well!

[KevinH]

Hi,

On a related note, is there some place where all of the <mbp:*> style tags are given in a list with something to indicate if they are block or inline types of tags.

The right way to handle prettyprint is to actually include these tags (since they will be seen in ebooks) into how prettyprint classifies inline vs structural vs block vs other tags.

Any pointer to a reference with a complete list of mbp tags would be appreciated.

Thanks,

KevinH

[Doitsu]

Originally Posted by KevinH

Any pointer to a reference with a complete list of mbp tags would be appreciated.

Here you go: Mobipocket Custom Tags

BTW, the Kindle Publishing Guidelines only list tags needed to create dictionaries.

[Billi]

Originally Posted by KevinH

Hi eschwartz,

Would you by any chance have access to an Arch Linux machine that runs Plasma 5. We have a bug report that all versions of Sigil (all current and all earlier) are segfaulting on Arch Linux ONLY when running the Plasma 5 Desktop (with Qt5.5) but running okay if any other Desktop is used. I have nothing to try and track that down with. I am guessing it is a conflict between Qt 5.5 and Plasma 5 that Sigil somehow triggers.

Thanks,

KevinH

Not directly Arch, but in Kaos, that uses Plasma5, there are big problems with Sigil:
http://kaosx.us/phpBB3/viewtopic.php?f=10&t=1147

[KevinH]

Hi,

yes I will look into it. My guess is it simply is an issue with Qt 5.5 and Plasma 5 that Sigil is triggering. eschwartz has set me up with a ssh account and I plan to give things a look this weekend. But right now I am stuck trying to help DiapDealer figure out why gumbo and Windows are not getting along.

I use a Linux Mint 17 build with Cinamon and all functions just fine. So it is some interaction with the Desktop that is causing the issue. It may not be Qt 5.5 directly, as other desktops with Qt 5.5 work just fine. It is just Plasma 5 that seems to be an issue.

Please tell your packager that Sigil 0.8.X branch is no longer supported (especially on clang) as it had issues with undefined behaviour with "Null" References. So we have had to rework the entire code base.

Only Sigil master should be worried about at this point and it has removed lots of dependencies and added a few others. There is a docs/Building on Linux.md that they should follow along with to get master building properly along with a number of python 3.4 site.packages that need to be in place.

Thanks for the head's up. I will let you know if I can figure anything out this weekend to help resolve the issue with Plasma 5.

KevinH

ps. I looked at the Qt bugreports and even QtCreator from 5.5 will not launch on Plasma 5 but will work properly with other Desktops. Qt's response was that Plasma 5 is experimental and to refile the bug report if it still failed on Plasma 4.

So will you simply try running the Qt's official QtCreator from Qt under Plasma 5 and report back if it still fails. If so, there is little hope to get Sigil running in Plasma 5 since our gui is much more complicated.

Thanks,

KevinH

Originally Posted by Billi

Not directly Arch, but in Kaos, that uses Plasma5, there are big problems with Sigil:
http://kaosx.us/phpBB3/viewtopic.php?f=10&t=1147

[donsanchezz]

Here is the bug. Win10x64. Sigil 0.8.9x64. Open Sigil-> open epub book -> service -> add cover. After adding edited cover from this epub-book, application will hung.
Solving: Downgrade to 0.87

[KevinH]

Hi,

Already reported and fixed in master. The fix will be int eh next release.

Thanks,

Kevin

Originally Posted by donsanchezz

Here is the bug. Win10x64. Sigil 0.8.9x64. Open Sigil-> open epub book -> service -> add cover. After adding edited cover from this epub-book, application will hung.
Solving: Downgrade to 0.87