Re: [sword-devel] Crash when getting module type

2023-10-31 Thread David "Judah's Shadow" Blue
Found my issue. I had a locally scoped library object that had it's own uninitalized swordLibrary that was taking precidence 🤦🏻, now I'm getting no crashes. I have other issues but that's for another email. ___ sword-devel mailing list: sword-devel@c

Re: [sword-devel] Crash when getting module type

2023-10-30 Thread David "Judah's Shadow" Blue
On Sunday, October 29, 2023 2:21:12 PM EDT Troy A. Griffitts wrote: > Hi David, > > On October 29, 2023 10:52:50 MST, "David "Judah's Shadow" Blue" wrote: > >The next class at play is the library class that also has a private member > >swordLibrary, > > > >sword::SWMgr swordLibrary; > > This is th

Re: [sword-devel] Crash when getting module type

2023-10-29 Thread Troy A. Griffitts
Important typo: - We could set option values from the source to the destination, I suppose, but still that would give you what you want. + We could set option values from the source to the destination, I suppose, but still that WOULDN'T give you what you want. On October 29, 2023 11:21:12 MST,

Re: [sword-devel] Crash when getting module type

2023-10-29 Thread Troy A. Griffitts
Hi David, On October 29, 2023 10:52:50 MST, "David "Judah's Shadow" Blue" wrote: >The next class at play is the library class that also has a private member >swordLibrary, > >sword::SWMgr swordLibrary; This is the issue. Since you are declaring an instance of SWMgr here, it will get constru

Re: [sword-devel] Crash when getting module type

2023-10-29 Thread David "Judah's Shadow" Blue
On Friday, October 27, 2023 1:25:44 PM EDT Troy A. Griffitts wrote: > I don't believe the issue is between when you declare the tempMod > variable and when you assign it. > > I believe the issue is between when you construct SWMgr() and when you > get to your code block. Somebody has done somethin

Re: [sword-devel] Crash when getting module type

2023-10-27 Thread Troy A. Griffitts
On 10/27/23 09:33, David "Judah's Shadow" Blue wrote: On Friday, October 27, 2023 8:46:19 AM EDT Troy A. Griffitts wrote: Hi David. There shouldn't be any nulls in the SWMgr::Modules map. Have you done anything with the map which might have created an entry? For example, have you attempted to o

Re: [sword-devel] Crash when getting module type

2023-10-27 Thread David "Judah's Shadow" Blue
On Friday, October 27, 2023 8:46:19 AM EDT Troy A. Griffitts wrote: > Hi David. There shouldn't be any nulls in the SWMgr::Modules map. Have you > done anything with the map which might have created an entry? For example, > have you attempted to obtain a module by name which wasn't there? In C++ >

Re: [sword-devel] Crash when getting module type

2023-10-27 Thread Troy A. Griffitts
Hi David. There shouldn't be any nulls in the SWMgr::Modules map. Have you done anything with the map which might have created an entry? For example, have you attempted to obtain a module by name which wasn't there? In C++ this would create an empty entry with a null pointer if the KJV wasn't i

Re: [sword-devel] Crash when getting module type

2023-10-26 Thread David "Judah's Shadow" Blue
On Wednesday, October 25, 2023 6:22:54 PM EDT Donna Whisnant wrote: > David, > > Based on the code you are showing, I can pretty much guarantee you that your > segfault is caused by tempMod being a null pointer -- i.e. that the value > of the map element you are iterating is null. Ok, I didn't kno

Re: [sword-devel] Crash when getting module type

2023-10-25 Thread Donna Whisnant
only shows iterating something that appears to be a std::map. Donna > Date: Tue, 24 Oct 2023 16:04:03 -0400 > From: "David \"Judah's Shadow\" Blue" > Subject: [sword-devel] Crash when getting module type > Message-ID: <5986010.lOV4Wx5bFT@brooks> > Conten

[sword-devel] Crash when getting module type

2023-10-24 Thread David "Judah's Shadow" Blue
I've resumed working on bibish some, and I'm getting a weird crash I never had before. I'm trying to interate through the list of installed modules and select those that match a given type. This is my code: for(libraryIterator = swordLibrary.Modules.begin(); libraryIterator != swordLi

[sword-devel] Crash when looking up module key in Nave module

2021-09-28 Thread Tobias Klein
Hi Troy, When trying to look up the key for the /Nave/ dictionary I got a crash. I am using a recent SWORD revision. Program received signal SIGSEGV, Segmentation fault. 0x7fc7c47dab82 in ?? () from /lib/x86_64-linux-gnu/libc.so.6 (gdb) bt #0  0x7fc7c47dab82 in ?? () from /lib/x86_64-l

Re: [sword-devel] Crash in Sword trunk (svn 3696) on Windows 10

2020-02-08 Thread Tobias Klein
Hi Troy, Thanks for looking into this! I've been using the VS2015 compiler for building Sword on Windows, because it works well with the "node-addon-api" (for creating native node.js modules). The necessary build tools can even be installed in a scripted fashion quite easily with npm (the node

Re: [sword-devel] Crash in Sword trunk (svn 3696) on Windows 10

2020-02-08 Thread Troy A. Griffitts
Hi Tobias, I've looked at the revisions you cite below. The first adds varargs to SWBuf and the second seems to simply fully qualify the icu namespace in the RegEx code which is used if you compile with ICU RegEx support. Can you give me a bit more information.  I think you might be the first on

[sword-devel] Crash in Sword trunk (svn 3696) on Windows 10

2020-02-06 Thread Tobias Klein
Hi, the latest Sword trunk crashes on Windows 10 during initialization of SWMgr. I built the library using Visual Studio 2015. EXCEPTION_ACCESS_VIOLATION_READ Fatal Error: EXCEPTION_ACCESS_VIOLATION_READ * * VCRUNTIME140+0x000332d|memcpy|memcpy.asm:668 * libsword+0x000ce

Re: [sword-devel] Crash in VersificationMgr::System::getBookCount (SWORD 1.8.1)

2018-06-14 Thread Karl Kleinpaste
On 06/14/2018 05:13 PM, Manfred Bergmann wrote: > Can that be reproduced in Xiphos or other frontends? No. Xiphos 4.1.0+ is happy with rusSYN1876eb. The method is in src/mgr/versificationmgr.cpp and is not used by Xiphos directly, and only by src/keys/versekey.cpp internally to Sword. If 'p' is t

[sword-devel] Crash in VersificationMgr::System::getBookCount (SWORD 1.8.1)

2018-06-14 Thread Manfred Bergmann
Hi. I’ve received one report where SWORD seems to crash on the above method for modules: - eBible.org/Biblical Texts/rusSYN1876eb (version 3.32) - IBT/Commentaries/BARC (version 1.0) - IBT/Commentaries/NGSB (version 1.0) I could reproduce that for rusSYN1876eb where in the code „p“ is NULL and h

Re: [sword-devel] crash using thml modules with strongs numbers

2003-06-20 Thread Martin Gruner
Yeah, that fixed the bug I reported as well. Thanks. mg Am Freitag, 20. Juni 2003 18:26 schrieb Joachim Ansorg: > Terry, > thank you for the detailt. > > > BibleTime will display both but crashes if I turn strongs numbers on. > > Just updated Bibletime about an hour ago. > > Thanks for the bug re

Re: [sword-devel] crash using thml modules with strongs numbers

2003-06-20 Thread Will Thimbleby
Fixed my bug too. Cheers Will On Friday, June 20, 2003, at 06:06 pm, Terry Biggs wrote: Thanks Joachim, That fixed it :) -- Terry <[EMAIL PROTECTED]> Rev 1:5 And from Jesus Christ, who is the faithful witness, and the first begotten of the dead, and the prince of the kings of the earth. Unt

Re: [sword-devel] crash using thml modules with strongs numbers

2003-06-20 Thread Terry Biggs
Thanks Joachim, That fixed it :) -- Terry <[EMAIL PROTECTED]> Rev 1:5 And from Jesus Christ, who is the faithful witness, and the first begotten of the dead, and the prince of the kings of the earth. Unto him that loved us, and washed us from our sins in his own blood http://gnomesword.sf.net

Re: [sword-devel] crash using thml modules with strongs numbers

2003-06-20 Thread Joachim Ansorg
Terry, thank you for the detailt. > BibleTime will display both but crashes if I turn strongs numbers on. > Just updated Bibletime about an hour ago. Thanks for the bug report. I wasn't aware of this bug! I thin kit's fixed now. In the ThMLMorph filter I wrote "token += token" instead of "text

Re: [sword-devel] crash using thml modules with strongs numbers

2003-06-19 Thread Terry Biggs
Joachim, the tr and the whnu are the modules. gnomesword will crash if I try to display either module. BibleTime will display both but crashes if I turn strongs numbers on. Just updated Bibletime about an hour ago. hope this helps On Thu, 2003-06-19 at 18:15, Joachim Ansorg wrote: > Terry, >

Re: [sword-devel] crash using thml modules with strongs numbers

2003-06-19 Thread Joachim Ansorg
Terry, I did some small tests and fixed some small suspicious things. But I can't get it crashing even without them. Can you tell me which module and what key make the code crash? Thanks, Joachim -- <>< Re: deemed! ___ sword-devel mailing list [EMAI

Re: [sword-devel] crash using thml modules with strongs numbers

2003-06-19 Thread Joachim Ansorg
Terry, I worked on the filters to make them use the new XMLTag stuff. Let me have a look at it. Maybe I made things buggy. I think it should be fixed soon. I'm sorry for the trouble, Joachim > Hello all, > > I've been working on this for about 3 hours and have made no progress. > gnomesword cras

[sword-devel] crash using thml modules with strongs numbers

2003-06-19 Thread Terry Biggs
Hello all, I've been working on this for about 3 hours and have made no progress. gnomesword crashes when you try to display a thml module with strongs numbers. Does not matter is the strongs option is on or off. here is a backtrace: 0x40e76326 in waitpid () from /lib/libc.so.6 #0 0x40e76326 in

Re: [sword-devel] Crash on module name w/ spaces

2002-07-03 Thread Troy A. Griffitts
Christian, I understand your asthetic disagreement, but the module name was intended to be a small abbreviation for the module and as a token to reference the module in code. The module Discription and About sections are intended more for user asthetics. Maybe CEDICTEn might be a bett

Re: [sword-devel] Crash on module name w/ spaces

2002-07-03 Thread Christian Renz
> Yes, spaces are NOT valid in module names, only alpha-numeric and > '_'. I changed my module names to, e.g. CEDICT_En Thanks, I didn't know that (didn't see it in the docs) and will change it. However, I think it is a nonnecessary limitation... or maybe the GUI interfaces should c

Re: [sword-devel] Crash on module name w/ spaces

2002-07-03 Thread Troy A. Griffitts
Christian, Yes, spaces are NOT valid in module names, only alpha-numeric and '_'. I changed my module names to, e.g. CEDICT_En -Troy. Christian Renz wrote: > Hi, > > a little bug report for Beta J: It seems not to be able to cope with > modules that have a space in t

[sword-devel] Crash on module name w/ spaces

2002-07-03 Thread Christian Renz
Hi, a little bug report for Beta J: It seems not to be able to cope with modules that have a space in their name, e.g. "CEDICT En". The message that comes up after starting sword is '"LexDictRTFCEDICT En" is not a valid component name'. This bug did not appear in previous versions of sword. Gree

[sword-devel] Crash!

2002-07-03 Thread Richard Guay
Hi, I opened the latest version of Sword for Windows and it came up in the Thai KJV Luke 16:19 with the Wesley Commentary showing. I changed to KJV Job 3:25 and accessed the MHC module. A dialog came up "Read access violation at address 05660E7 in module "Sword.exe" Read of address 202C6469