Homebrew RELEASE Noexs Remote Debugger

  • Thread starter Thread starter matt123337
  • Start date Start date
  • Views Views 189,664
  • Replies Replies 664
  • Likes Likes 25
I've been spending many hours running it now without success.
JAVA 10 already has the JAVA FX with you.
Only always comes the same message:

at.me.mdbell.noexs.core.ConnectionException: Result{mod=349, desc=9}
at me.mdbell.noexs.core.Debugger.readInfo(Debugger.java:525)
at me.mdbell.noexs.core.Debugger.query(Debugger.java:375)
at me.mdbell.noexs.dump.DumpRegionSupplier$2.init(DumpRegionSupplier.java:82)
at me.mdbell.noexs.dump.DumpRegionSupplier$2.getSize(DumpRegionSupplier.java:73)
at me.mdbell.noexs.ui.services.MemorySearchService$SearchTask.createDump(MemorySearchService.java:334)
at me.mdbell.noexs.ui.services.MemorySearchService$SearchTask.fullSearch(MemorySearchService.java:244)
at me.mdbell.noexs.ui.services.MemorySearchService$SearchTask.call(MemorySearchService.java:189)
at me.mdbell.noexs.ui.services.MemorySearchService$SearchTask.call(MemorySearchService.java:172)
at javafx.graphics/javafx.concurrent.Task$TaskCallable.call(Unknown Source)
at java.base/java.util.concurrent.FutureTask.run(Unknown Source)
at javafx.graphics/javafx.concurrent.Service.lambda$executeTask$6(Unknown Source)
at java.base/java.security.AccessController.doPrivileged(Native Method)
at javafx.graphics/javafx.concurrent.Service.lambda$executeTask$7(Unknown Source)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.base/java.lang.Thread.run(Unknown Source)

Did anyone send me the JAVA folder?
 
Last edited by merlin555,
I also have the same mistake in searching:

Have installed:

jdk-10.0.2_windows-x64_bin.exe

But no JAVA FX ..
Where can I find this for Windows for Java 10?
(with installer)

Error:
me.mdbell.noexs.core.ConnectionException: Result{mod=349, desc=9}
at me.mdbell.noexs.core.Debugger.readInfo(Debugger.java:525)
at me.mdbell.noexs.core.Debugger.query(Debugger.java:375)
at me.mdbell.noexs.dump.DumpRegionSupplier$2.init(DumpRegionSupplier.java:82)
at me.mdbell.noexs.dump.DumpRegionSupplier$2.getSize(DumpRegionSupplier.java:73)
at me.mdbell.noexs.ui.services.MemorySearchService$SearchTask.createDump(MemorySearchService.java:334)
at me.mdbell.noexs.ui.services.MemorySearchService$SearchTask.fullSearch(MemorySearchService.java:244)
at me.mdbell.noexs.ui.services.MemorySearchService$SearchTask.call(MemorySearchService.java:189)
at me.mdbell.noexs.ui.services.MemorySearchService$SearchTask.call(MemorySearchService.java:172)
at javafx.graphics/javafx.concurrent.Task$TaskCallable.call(Unknown Source)
at java.base/java.util.concurrent.FutureTask.run(Unknown Source)
at javafx.graphics/javafx.concurrent.Service.lambda$executeTask$6(Unknown Source)
at java.base/java.security.AccessController.doPrivileged(Native Method)
at javafx.graphics/javafx.concurrent.Service.lambda$executeTask$7(Unknown Source)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.base/java.lang.Thread.run(Unknown Source)
You have javafx, you need to attach to a process before debugging. Noexes is module 349, and see here for what each error means:
https://github.com/mdbell/Noexes/blob/master/server/source/noexs/include/errors.h#L17

Has to be 10? I use 11.0.1...I thought a higher version was okay, but lower was not.
Java has made a bunch of changes in 11, to make it modular. Updating to 11 is on my to-do list, just won't be till the new year.
 
Had the problem also short when sampling.

Uninstall times all JAVA programs
and then delete the JAVA folder in "Program files"
and in the folder "Program files (86)" also the JAVA folder
 
to be clearer even if the files look the same drag and drop javafx sdk folders into the java folder in program files x86 or program files. I never tested it. I'm not referring to jmods
 
I think it's more set on how you set your PATH variables.

For example, I'm running 64 bit Win 10 and this is what my dir structure looks like, in Program Files (x86) I only have v 1.8.0 but in Program Files I have both 10 and 11, but I set my PATH variable to point to the correct bin folder and all is well.

C:\Program Files (x86)\Java
jdk1.8.0_192
jre1.8.0_192

C:\Program Files\Java
jdk-10.0.2
jre-10.0.2
jdk-11.0.1
jre1.9.0_191
jdk1.9.0_161

--------------------- MERGED ---------------------------

And check this file

Load by Launch the CFW!

What does this have to do with anything? Those are just the files anyone can download from https://www.sdsetup.com/console?switch
 
Is it going now ?
Already searching ?

--------------------- MERGED ---------------------------

Said only if it is not possible to check.
 
Most likely because you don't have debug permissions set. I don't know if SX OS has a way to do that. Someone more knowledgeable about SX OS would have to tell you if there's a setting you can change somewhere that does it.
 
Most likely because you don't have debug permissions set. I don't know if SX OS has a way to do that. Someone more knowledgeable about SX OS would have to tell you if there's a setting you can change somewhere that does it.

How would I set debug permission? I'm loading Hekate and Atmosphere
 
[Noexes]
debugmode=1
kip1=modules/kips/loader.kip
kip1=modules/kips/sm.kip
kip1=modules/kips/noexs.kip1
kip1=modules/kips/nx-dreport.kip


I have my Hekate_ipl.nil set like this
[config]
autoboot=0
bootwait=5
customlogo=1
verification=2

{-- NSwitchDebugger --}
[Noexs]
kip1=modules/nsdebugger/loader.kip
kip1=modules/newfirm/sm.kip
kip1=noexs.kip1
fullsvcperm=1
kip1patch=nosigchk
atmosphere=1
debugmode=1
fullsvcperm=1
 
  • Like
Reactions: merlin555
For Atmosphere, edit BCT.ini and under the [exosphere] make sure debugmode = 1 is set and launch Atmosphere using fusee-primary.bin, for Hekate edit whatever boot ini you're using and add debugmode=1 to it. This is the ini I made for Hekate to use it

Code:
{-------- Noexs -------}
[Noexs]
kip1=modules/required/loader.kip
kip1=modules/required/pm.kip
kip1=modules/required/sm.kip
kip1=modules/noexs/noexs.kip1
secmon=modules/required/exosphere.bin
atmosphere=1
debugmode=1
{ }
Make sure your ini is pointing to the correct location of the kip file. That's why mine says modules/noexs/noexs.kip1 as that's the folder I put it in, before switching to full atmosphere. I should also point out if you're using an NSP of something you didn't buy you'll also need the nosigchk option enabled.
 
Last edited by Deathwing Zero,
  • Like
Reactions: merlin555
I still can't searching.
Or do you have to do something beforehand in the Jnoexsclient?

java -jar jnoexsclient.jar ?

Error:
C:\Program Files\Java\jdk-9.0.4\bin>java -jar C:\_ROMS\Pointer\jnoexsclient.jar
at.me.mdbell.noexs.core.ConnectionException: Result{mod=349, desc=9}
at me.mdbell.noexs.core.Debugger.readInfo(Debugger.java:525)
at me.mdbell.noexs.core.Debugger.query(Debugger.java:375)
at me.mdbell.noexs.dump.DumpRegionSupplier$2.init(DumpRegionSupplier.java:82)
at me.mdbell.noexs.dump.DumpRegionSupplier$2.getSize(DumpRegionSupplier.java:73)
at me.mdbell.noexs.ui.services.MemorySearchService$SearchTask.createDump(MemorySearchService.java:334)
at me.mdbell.noexs.ui.services.MemorySearchService$SearchTask.fullSearch(MemorySearchService.java:244)
at me.mdbell.noexs.ui.services.MemorySearchService$SearchTask.call(MemorySearchService.java:189)
at me.mdbell.noexs.ui.services.MemorySearchService$SearchTask.call(MemorySearchService.java:172)
at javafx.graphics/javafx.concurrent.Task$TaskCallable.call(Task.java:1425)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
at javafx.graphics/javafx.concurrent.Service.lambda$executeTask$6(Service.java:725)
at java.base/java.security.AccessController.doPrivileged(Native Method)
at javafx.graphics/javafx.concurrent.Service.lambda$executeTask$7(Service.java:724)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
at java.base/java.lang.Thread.run(Thread.java:844)
 
Haven not slept all night because of this.
But you just have to read the instructions correctly:-)
First in the tools menu and pick up the PID etc.

--------------------- MERGED ---------------------------

only working java:

jdk-9.0.4
jre-9.0.4
jdk-10.0.2
jre-10.0.2

Java 11 dont work!
 

Site & Scene News

Popular threads in this forum