Search found 313 matches

by wwhite
2024 Jan 10, 23:42
Forum: Hardware, Programming & Disassembly
Topic: SAD Version 5 (alpha)
Replies: 136
Views: 12486

Re: SAD Version 5 (alpha)

Here's a good one, actually probably a really bad bug.

Who see's the problem with this one:

Code: Select all

7de5: 14,01                     #arg 1              114,
7de7: d6,f0                     #arg 2              f0d6,
7deb: 28,03                     #arg 3              328,
7ded: 34,03                     #arg 4              334 );  
What happened to address 0x7de9 and 0x7dea ?
by wwhite
2024 Jan 10, 22:55
Forum: Hardware, Programming & Disassembly
Topic: SAD Version 5 (alpha)
Replies: 136
Views: 12486

Re: SAD Version 5 (alpha)

5.0.5, better, sort of, doesn't seg fault.
Creates lst and msg files, no dbg.
Once I add dir, program hangs or is stuck in a loop, at: | Analyse Data Structs

Old dir:

Code: Select all

args    76af 76b2 : O 2 UY  : UW N 
args    772c 772f : O 2 UY  : UW N 
word    7732 7733

7729: ef,bf,04            call  7beb             Sub_7beb (
772c: 0f                        #arg 1              f,
772d: 02                        #arg 2              2,
772e: 80,a7                     #arg 3              a780 );
7730: 20,11               sjmp  7743             goto 7743;

7732: 34,77               word   7734
New dir:

Code: Select all

args    76af  76b2     [ UY ][ UY ][ UY ][ UW N ]
args    772c  772f     [ UY ][ UY ][ UY ][ UW N ]
word    7732  7733     

7729: ef,bf,04            call  7beb             Sub_7beb (
772c: 0f                        #arg 1              f,
772d: 02                        #arg 2              2,
772e: 80                        #arg 3              80,
772f: a7,20                     #arg 4              20a7 );
7732: 34,77,04            jnb   B4,R77,7739      if (B4_R77 = 1) {
Sad 5.0.5 is creating too many args, there should be two(2) byte args and one(1) word arg for a total of three(3) args, not four(4) args.
by wwhite
2024 Jan 09, 20:48
Forum: Hardware, Programming & Disassembly
Topic: SAD Version 5 (alpha)
Replies: 136
Views: 12486

Re: SAD Version 5 (alpha)

I get exact same seg fault as before using 5.0.4

Code: Select all

Reading symbols from SAD_5.0.4.exe...
(gdb) run
Starting program: C:\Users\wwhite\Programming\SAD\SAD_5.0.4.exe
[New Thread 14704.0x3b80]
KID2

Thread 1 received signal SIGSEGV, Segmentation fault.
0x0040c25a in add_spf_register (p=0xce1c90, dest=58, sce=0, popaddr=622135)
    at C:/CLProjects/SAD/WSAD/Core.cpp:6205
warning: Source file is more recent than executable.
6205
(gdb) bt
#0  0x0040c25a in add_spf_register (p=0xce1c90, dest=58, sce=0,
    popaddr=622135) at C:/CLProjects/SAD/WSAD/Core.cpp:6205
#1  0x0040c7fe in ldx (s=0xc2898c, c=0x438720 <einst>)
    at C:/CLProjects/SAD/WSAD/Core.cpp:6522
#2  0x0040f036 in do_code (s=0xc2898c, c=0x438720 <einst>)
    at C:/CLProjects/SAD/WSAD/Core.cpp:8107
#3  0x0040a2db in scan_blk (s=0xc2898c, c=0x438720 <einst>)
    at C:/CLProjects/SAD/WSAD/Core.cpp:3689
#4  0x0040e40e in scl (s=0xc28c44, c=0x438720 <einst>)
    at C:/CLProjects/SAD/WSAD/Core.cpp:7580
#5  0x0040f036 in do_code (s=0xc28c44, c=0x438720 <einst>)
    at C:/CLProjects/SAD/WSAD/Core.cpp:8107
#6  0x0040a2db in scan_blk (s=0xc28c44, c=0x438720 <einst>)
    at C:/CLProjects/SAD/WSAD/Core.cpp:3689
#7  0x0040a46b in emulate_blk (addr=623014, caller=0xceab88)
    at C:/CLProjects/SAD/WSAD/Core.cpp:3860
#8  0x0040e13e in do_sub_scan (caller=0xceab88, c=0x438660 <cinst>)
    at C:/CLProjects/SAD/WSAD/Core.cpp:7435
#9  0x0040e354 in scl (s=0xceab88, c=0x438660 <cinst>)
    at C:/CLProjects/SAD/WSAD/Core.cpp:7540
#10 0x0040f036 in do_code (s=0xceab88, c=0x438660 <cinst>)
    at C:/CLProjects/SAD/WSAD/Core.cpp:8107
#11 0x0040a2db in scan_blk (s=0xceab88, c=0x438660 <cinst>)
    at C:/CLProjects/SAD/WSAD/Core.cpp:3689
#12 0x0040f736 in scan_all () at C:/CLProjects/SAD/WSAD/Core.cpp:8520
#13 0x004123cc in disassemble (fstr=0xce1658 "KID2")
    at C:/CLProjects/SAD/WSAD/Core.cpp:10579
#14 0x00422bee in main (argc=1, argv=0xce1678)
    at C:/CLProjects/SAD/WSAD/main.cpp:593
(gdb)

by wwhite
2024 Jan 05, 16:19
Forum: Hardware, Programming & Disassembly
Topic: SAD Version 5 (alpha)
Replies: 136
Views: 12486

Re: SAD Version 5 (alpha)

Both, yes.

Get same back trace and seg fault same location with precompiled binary.
by wwhite
2024 Jan 05, 02:57
Forum: Hardware, Programming & Disassembly
Topic: SAD Version 5 (alpha)
Replies: 136
Views: 12486

Re: SAD Version 5 (alpha)

Spoke too soon.
Works with no dir file, and with a dir file it seg faults still.
by wwhite
2024 Jan 05, 02:42
Forum: Hardware, Programming & Disassembly
Topic: SAD Version 5 (alpha)
Replies: 136
Views: 12486

Re: SAD Version 5 (alpha)

Well, I commented out line# 6508 in core.cpp, and it works!!

I have no idea what the following does, but for single bank its good.

Code: Select all

6508: //add_spf_register(p, o->addr, 0, c->opr[1].addr); 
Screenshot 2024-01-04 234023.png
by wwhite
2024 Jan 05, 02:07
Forum: Hardware, Programming & Disassembly
Topic: SAD Version 5 (alpha)
Replies: 136
Views: 12486

Re: SAD Version 5 (alpha)

Here is a full back trace:

Code: Select all

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
by wwhite
2024 Jan 05, 01:49
Forum: Hardware, Programming & Disassembly
Topic: SAD Version 5 (alpha)
Replies: 136
Views: 12486

Re: SAD Version 5 (alpha)

The program seg faults same location as pre 5.0.3.
Screen shots attached:
Screenshot 2024-01-04 224456.png
Screenshot 2024-01-04 224542.png
by wwhite
2024 Jan 05, 01:14
Forum: Hardware, Programming & Disassembly
Topic: SAD Version 5 (alpha)
Replies: 136
Views: 12486

Re: SAD Version 5 (alpha)

$ ./SAD_5.0.3.exe KID2
Segmentation fault

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.

I created a pull request:

Code: Select all

 
Development/NEW*NEW version 5 readme.txt → Development/NEW-NEW version 5 readme.txt
Asterisk * in the file name prevents git clone working.
by wwhite
2024 Jan 03, 10:48
Forum: A1C - 80/90s EFI-SD4x Speed Density
Topic: E4OD Calibration Constants
Replies: 20
Views: 6234

Re: E4OD Calibration Constants

Anyone used the SAD806x windows gui?
The developer goes by the name 'thepym'.
Windows executable here: https://github.com/OpenEEC-Project/SAD8 ... master/Exe

It has built in database to save info like what is in the above spreadsheet.
And has built in create XDF file for TunerPro.

I had it working a couple years ago, wasn't perfect.

I'm wondering if using this tool is better for managing multiple bins.
Screenshot 2024-01-03 074615.png
Screenshot 2024-01-03 074629.png