Vehicle Information: 1999 Ford Ranger with 2000 Explorer v8 swap, FLN0 2003 Ford F150 Harley Davidson, Built 5.4L SOHC with 3.4L Whipple and Built 4R100
I will give it a try without the dir and cmt files and see what I get.
EDIT: Yep, that worked. must be something about my dir file it doesn't like. I will go through it this weekend some more and double check for duplicates, and just delete the entries I have edited out with a # at the start of the line. I have a ton of garbled up mess in my dir file, I keep going back and changing things as I find them and sometimes I keep going back and forth questioning my choices. Also the dir works with v4.16b but maybe isn't completely compatible with v5, so I will check my entries with the V5 command list.
EDIT: SAD V5.0.2 definitely crashes with my dir file. The dbg file ends very abruptly with this
Vehicle Information: 1999 Ford Ranger with 2000 Explorer v8 swap, FLN0 2003 Ford F150 Harley Davidson, Built 5.4L SOHC with 3.4L Whipple and Built 4R100
Yes, Thank You! Without this software we would be lost. And Everyone's help, of course.
EDIT: I just tried it with a DIR file and get empty msg and lst files. The post above where it shows where the dbg file stops, is that a clue for me to fix something in my dir file that may be stopping SAD from finishing the disassembly? If so, Where do I start looking? Thanks again very much for all of your hard work.
Not good.
Sure would be nice if you used the GIT repository the way it is meant to be used, so other developers could see the changes, and compare diff.
I know I've asked before, and you've answered me before.
I sure would like to contribute, but not committing changes to the git repo makes it impossible to share code and for others to fix bugs.
Just my opinion.
Reading symbols from sad.exe...
Starting program: sources\5.0.3\sad.exe
[New Thread 11492.0x2bb8]
KID2
Thread 1 received signal SIGSEGV, Segmentation fault.
add_spf_register (p=0xaa6ba8, dest=58, sce=0, popaddr=622135) at sources\5.0.3\core.cpp:6191
6191 if (!get_spf(vconv(p->argblk[1]->nextaddr)))
#0 add_spf_register (p=0xaa6ba8, dest=58, sce=0, popaddr=622135) at sources\5.0.3\core.cpp:6191
#1 0x00007ff6df544f9c in ldx (s=0x9b3540, c=0x7ff6df573ca0 <einst>) at sources\5.0.3\core.cpp:6508
#2 0x00007ff6df547b1a in do_code (s=0x9b3540, c=0x7ff6df573ca0 <einst>) at sources\5.0.3\core.cpp:8093
#3 0x00007ff6df5427ed in scan_blk (s=0x9b3540, c=0x7ff6df573ca0 <einst>) at sources\5.0.3\core.cpp:3681
#4 0x00007ff6df546d62 in scl (s=0x9b3270, c=0x7ff6df573ca0 <einst>) at sources\5.0.3\core.cpp:7566
#5 0x00007ff6df547b1a in do_code (s=0x9b3270, c=0x7ff6df573ca0 <einst>) at sources\5.0.3\core.cpp:8093
#6 0x00007ff6df5427ed in scan_blk (s=0x9b3270, c=0x7ff6df573ca0 <einst>) at sources\5.0.3\core.cpp:3681
#7 0x00007ff6df5429c0 in emulate_blk (addr=623014, caller=0xab3b90) at sources\5.0.3\core.cpp:3852
#8 0x00007ff6df546a78 in do_sub_scan (caller=0xab3b90, c=0x7ff6df573be0 <cinst>) at sources\5.0.3\core.cpp:7421
#9 0x00007ff6df546ca5 in scl (s=0xab3b90, c=0x7ff6df573be0 <cinst>) at sources\5.0.3\core.cpp:7526
#10 0x00007ff6df547b1a in do_code (s=0xab3b90, c=0x7ff6df573be0 <cinst>) at sources\5.0.3\core.cpp:8093
#11 0x00007ff6df5427ed in scan_blk (s=0xab3b90, c=0x7ff6df573be0 <cinst>) at sources\5.0.3\core.cpp:3681
#12 0x00007ff6df54819a in scan_all () at sources\5.0.3\core.cpp:8506
#13 0x00007ff6df54ad9f in disassemble (fstr=0xaa6510 "KID2") at sources\5.0.3\core.cpp:10565
#14 0x00007ff6df54beee in main (argc=1, argv=0xaa3d30) at sources\5.0.3\main.cpp:593
Vehicle Information: 1999 Ford Ranger with 2000 Explorer v8 swap, FLN0 2003 Ford F150 Harley Davidson, Built 5.4L SOHC with 3.4L Whipple and Built 4R100
I am sorry, I spoke too soon as well, with a dir file I got a partial lst file and an empty msg file. No debug file this time. My lst file seems to end with a few func listings and then just stops. Is there a way to tell what made the program crash?
EDIT: Never mind. I went into my DIR file and commented out the functions list i had and the program completed the run. I got msg file and lst file. I did get a few errors for duplicate commands that I have to go in and check on, but other than that I need to look at the new documentation and see if something with how those functions are defined is not compatible with the new SAD. Great job on the error corrections in the software!! The rest is most likely me or outdated commands in my dir file.
These are my errors and will report back if it was my doing or maybe a bug. Thanks again!!!