-
Notifications
You must be signed in to change notification settings - Fork 363
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Build issue with new SDK #380
Comments
不,这个文件来自依赖而不是sdk,https://github.com/HyperDbg/phnt/blob/master/ntioapi.h 我的感觉是这个头文件内的结构体和sdk内的某个文件内定义的结构体重复导致编译错误,可能来自ntifs.h,我还没来得及搜索 |
Agree. By the way, in this casem it's an issue with |
也可以,那么这么长时间下来你每次编译都没有得到这个编译错误吗?如果是警告就不管它了,但重定义错误不能编译成功。我想象一下如果向源仓库报告,估计他那边也就是注释掉这么解决的。比如我们自己写的代码:定义一个结构体又复制一个同样的,这肯定不行,对于我们的仓库引用它的情况,我们也不可能不引用sdk使得重定义错误消失,这也行不通。所以我的建议是:在您fork的仓库内注释掉那几行就行了。但如果你们编译没有这个错误,就很奇怪,需要进一步讨论。
…---原始邮件---
发件人: "Sina ***@***.***>
发送时间: 2024年6月13日(周四) 下午2:09
收件人: ***@***.***>;
抄送: ***@***.******@***.***>;
主题: Re: [HyperDbg/HyperDbg] 重复的结构体导致编译错误 (Issue #380)
Agree. By the way, in this casem it's an issue with phnt. I think it should be fixed by them: https://github.com/winsiderss/phnt
It would be best if you could report it to their repo.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
No, this error never happens to me. I also asked a couple of friends and they didn't encounter this error. It seems that you're the first one that got this error. 🤔 |
这就很奇怪,这个错误是我第一次使用hyperdbg仓库至今都存在的编译错误。如果只有我一个人能复现,估计报告给源仓库他也不知道怎么解决。所以如果可以,我想邀请您远程我的电脑,这个我就每次更新仓库编译都修改代码。
…---原始邮件---
发件人: "Sina ***@***.***>
发送时间: 2024年6月13日(周四) 下午2:19
收件人: ***@***.***>;
抄送: ***@***.******@***.***>;
主题: Re: [HyperDbg/HyperDbg] 重复的结构体导致编译错误 (Issue #380)
No, this error never happens to me. I also asked a couple of friends and they didn't encounter this error. It seems that you're the first one that got this error. 🤔
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
That's not a big problem. If that's how it works on your computer, it's pretty fine. Fixing it by commenting the code doesn't hurt the code since this function is not used in HyperDbg. I think it's better to fix it this way and later once you install Visual Studio again, the problem will be solved for you. 这不是什么大问题。如果它在你的电脑上就是这样工作的,那就没问题了。通过注释代码来修复它不会损害代码,因为这个函数在 HyperDbg 中没有使用。我认为最好以这种方式修复它,稍后一旦你再次安装 Visual Studio,问题就会为你解决。 |
vs2022是昨天才新装的新版本,不过这确实可以解决,所以我关闭此议题。我将抽空更新gui,似乎一切准备就绪。 |
Maybe it's an issue with the newest version. I'll check it. 🤔 |
hi,请看 我这边是否需要实现模拟运行时? |
This issue (compile issue) was also mentioned in the HyperDbg telegram group. So, it seems that this problem happens to everyone who uses the latest SDK. I'll reopen it to be fixed. HyperDbg 电报群中也提到了这个问题(编译问题)。所以,似乎每个使用最新 SDK 的人都会遇到这个问题。我会重新打开它进行修复。 |
Adding macro define like this way can solve the problem to avoid redefinition . Follow this winsiderss/systeminformer@060790a |
Isn't it a problem with phnt? I think it should be solved by |
Sure we could solve it by commenting it on our fork of phnt since we're not using this structure in HyperDbg. |
ok,wait your dev commit
…---原始邮件---
发件人: "Sina ***@***.***>
发送时间: 2024年6月21日(周五) 中午1:35
收件人: ***@***.***>;
抄送: ***@***.***>;"State ***@***.***>;
主题: Re: [HyperDbg/HyperDbg] 重复的结构体导致编译错误 (Issue #380)
Sure we could solve it by commenting it on our fork of phnt since we're not using this structure in HyperDbg.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you modified the open/close state.Message ID: ***@***.***>
|
你是对的
…---原始邮件---
发件人: "Sina ***@***.***>
发送时间: 2024年6月21日(周五) 中午1:34
收件人: ***@***.***>;
抄送: ***@***.***>;"State ***@***.***>;
主题: Re: [HyperDbg/HyperDbg] 重复的结构体导致编译错误 (Issue #380)
Isn't it a problem with phnt? I think it should be solved by phnt authors, I created an issue here: winsiderss/phnt#34
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you modified the open/close state.Message ID: ***@***.***>
|
I updated the 'dev' branch to fix phnt error.
And confirm if it builds successfully in the latest SDK? |
I'm working on it now. |
中国的网络太糟糕了,假如你在仓库根目录下写入go模块,那么任何中国这边的开发者都可以使用go模块代理来加速下载。克隆和下载是一样的,go模块可以指定提交id拉取。 skia就是这样的: |
It is not ready yet, I'm currently working on renaming HPRDBGCTRL to 'libhyperdbg' (as I previously told you) and redesigning SDK functions to export your needed functions (such as memory read), it will be finished tonight. I'll let you know, once it's finished so you can use your requested functionalities (+ any new needed functions). 它还没有准备好,我目前正在将 HPRDBGCTRL 重命名为“libhyperdbg”(正如我之前告诉您的),并重新设计 SDK 函数以导出您所需的函数(例如内存读取),它将在今晚完成。一旦完成,我会通知您,以便您可以使用您请求的功能(+任何新的所需功能)。 |
此外,connect本地和远程相关的也要导出,现在物理机dll加载成功,但是我的测试是这样的:
物理机:加载dll,驱动
VMware:物理机上驱动加载成功之后,来到VMware就不会遇到那么多错误了,此时我们再次加载dll,connect,加载驱动,start,读取buffer反汇编呈现到gui。
到这一步时可以进入beta状态了。
…---Original---
From: "Sina ***@***.***>
Date: Mon, Jun 24, 2024 17:39 PM
To: ***@***.***>;
Cc: ***@***.***>;"State ***@***.***>;
Subject: Re: [HyperDbg/HyperDbg] Build issue with new SDK (Issue #380)
It is not ready yet, I'm currently working on renaming HPRDBGCTRL to 'libhyperdbg' (as I previously told you) and redesigning SDK functions to export your needed functions (such as memory read), it will be finished tonight. I'll let you know, once it's finished so you can use your requested functionalities (+ any new needed functions).
它还没有准备好,我目前正在将 HPRDBGCTRL 重命名为“libhyperdbg”(正如我之前告诉您的),并重新设计 SDK 函数以导出您所需的函数(例如内存读取),它将在今晚完成。一旦完成,我会通知您,以便您可以使用您请求的功能(+任何新的所需功能)。
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you modified the open/close state.Message ID: ***@***.***>
|
此外,为什么不把我在gui仓库论坛支出的两个目录全部都导出到dll呢,一次性全部都导出不是更好吗?
…---Original---
From: "Sina ***@***.***>
Date: Mon, Jun 24, 2024 17:39 PM
To: ***@***.***>;
Cc: ***@***.***>;"State ***@***.***>;
Subject: Re: [HyperDbg/HyperDbg] Build issue with new SDK (Issue #380)
It is not ready yet, I'm currently working on renaming HPRDBGCTRL to 'libhyperdbg' (as I previously told you) and redesigning SDK functions to export your needed functions (such as memory read), it will be finished tonight. I'll let you know, once it's finished so you can use your requested functionalities (+ any new needed functions).
它还没有准备好,我目前正在将 HPRDBGCTRL 重命名为“libhyperdbg”(正如我之前告诉您的),并重新设计 SDK 函数以导出您所需的函数(例如内存读取),它将在今晚完成。一旦完成,我会通知您,以便您可以使用您请求的功能(+任何新的所需功能)。
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you modified the open/close state.Message ID: ***@***.***>
|
Not sure if I understand what you mean. 🤔 不确定我是否明白你的意思。🤔 |
Export all .h file function in this dir:
https://github.com/HyperDbg/HyperDbg/tree/master/hyperdbg%2Fhprdbgctrl%2Fheader
…---Original---
From: "Sina ***@***.***>
Date: Mon, Jun 24, 2024 18:37 PM
To: ***@***.***>;
Cc: ***@***.***>;"State ***@***.***>;
Subject: Re: [HyperDbg/HyperDbg] Build issue with new SDK (Issue #380)
此外,为什么不把我在gui仓库论坛支出的两个目录全部都导出到dll呢,一次性全部都导出不是更好吗?
Not sure if I understand what you mean. 🤔
不确定我是否明白你的意思。🤔
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you modified the open/close state.Message ID: ***@***.***>
|
No, that's not a good idea since there are lots of internal functions that are designed for internal use, and don't make sense to be exported. Let's just export those functions that are really useful to the SDK. 不,这不是一个好主意,因为有很多内部函数是为内部使用而设计的,导出毫无意义。我们只导出那些对 SDK 真正有用的函数。 |
我无法构建成功
…---Original---
From: "Sina ***@***.***>
Date: Mon, Jun 24, 2024 18:59 PM
To: ***@***.***>;
Cc: ***@***.***>;"State ***@***.***>;
Subject: Re: [HyperDbg/HyperDbg] Build issue with new SDK (Issue #380)
No, that's not a good idea since there are lots of internal functions that are designed for internal use, and don't make sense to be exported. Let's just export those functions that are really useful to the SDK.
Anyway, did you check whether the build problem (commenting those structures in phnt) was fixed or not? If it's fixed, please close this issue as completed.
不,这不是一个好主意,因为有很多内部函数是为内部使用而设计的,导出毫无意义。我们只导出那些对 SDK 真正有用的函数。
无论如何,您是否检查过构建问题(在 phnt 中注释这些结构)是否已修复?如果已修复,请将此问题关闭为已完成。
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you modified the open/close state.Message ID: ***@***.***>
|
Did you removed an re-clone it using this command? |
因为中国网络很糟糕,我是这么操作的:
删除 .git 目录以外的文件,checkout到dev分支并rebase它,最后更新子模块那堆依赖,到这里网络卡住了,再次构建是失败的。假如用mod管理我就能快速下载所有依赖。
…---Original---
From: "Sina ***@***.***>
Date: Mon, Jun 24, 2024 19:05 PM
To: ***@***.***>;
Cc: ***@***.***>;"State ***@***.***>;
Subject: Re: [HyperDbg/HyperDbg] Build issue with new SDK (Issue #380)
Did you removed an re-clone it using this command?
git clone -b dev --recursive https://github.com/HyperDbg/HyperDbg.git
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you modified the open/close state.Message ID: ***@***.***>
|
No, the problem is that I removed 'phnt' as a submodule. So, I'm not sure if updating modules works or not. No problem, you can test it later once the network is stable. 不,问题是我删除了“phnt”作为子模块。所以,我不确定更新模块是否有效。没问题,您可以在网络稳定后稍后进行测试。 |
Now, build success, can be close. |
Describe the bug
这是一个一直以来都存在的问题,每次编译我都要注释掉这三个结构体,vs2022提示这三个结构体重定义
To Reproduce
Steps to reproduce the behavior:
clone 仓库编译即可看到错误
Expected behavior
0错误0警告的编译
Screenshots
![Screenshot_20240613_133119_com.realvnc.viewer.android.jpg](https://private-user-images.githubusercontent.com/19886504/339224737-b2ec527e-bff7-4360-aabc-7120292df6e8.jpg?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjIyMTU2MDksIm5iZiI6MTcyMjIxNTMwOSwicGF0aCI6Ii8xOTg4NjUwNC8zMzkyMjQ3MzctYjJlYzUyN2UtYmZmNy00MzYwLWFhYmMtNzEyMDI5MmRmNmU4LmpwZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDA3MjklMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwNzI5VDAxMDgyOVomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTMxZjc4MGE5YWYxNjU0ZmU1MzM3OWVhOWVhNDg2MDM4MGRhODdlYzY0YTMzZGFiNzE0MTcxZmM1NmQwNzc4NGMmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.T3CpVmqBfOl4H-kBJtAYQHAok3ak1ZnHo2Z-KXa1RoU)
Desktop (please complete the following information):
Windows X-Lite (22621.1928) 'Micro 11' By FBConan
Additional context
no more
The text was updated successfully, but these errors were encountered: