Skip to content
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

INFO[0029] exitHandler: cannot get the arguments from storehouse because of neverseen: pid: 730, inst: 174 #4

Closed
kissablemt opened this issue Dec 8, 2021 · 19 comments

Comments

@kissablemt
Copy link

不知道什么问题噢

@mzz2017
Copy link
Owner

mzz2017 commented Dec 8, 2021

什么cpu架构,如何复现

@kissablemt
Copy link
Author

树莓派arm的,gg curl 就会

@kissablemt
Copy link
Author

什么cpu架构,如何复现

难得在你这找到arm,git上找了好多都不支持arm

@mzz2017
Copy link
Owner

mzz2017 commented Dec 8, 2021

难得在你这找到arm,git上找了好多都不支持arm

好的,arm还没测试过,我会测试一下然后尝试修复,谢谢

@mzz2017
Copy link
Owner

mzz2017 commented Dec 8, 2021

我用 qemu 模拟了一下 arm,是可以使用的,只是会有这个报错信息。你那边可以正常使用吗?

@smartcatboy
Copy link

smartcatboy commented Dec 8, 2021

树莓派arm的,gg curl 就会

执行 lscpucat /proc/cpuinfo 的输出能发一下吗?

这是我在甲骨文 ARM64 机器上执行的结果,测试运行正常:

# lscpu:

Architecture:                    aarch64
CPU op-mode(s):                  32-bit, 64-bit
Byte Order:                      Little Endian
CPU(s):                          1
On-line CPU(s) list:             0
Thread(s) per core:              1
Core(s) per socket:              1
Socket(s):                       1
NUMA node(s):                    1
Vendor ID:                       ARM
Model:                           1
Model name:                      Neoverse-N1
Stepping:                        r3p1
BogoMIPS:                        50.00
NUMA node0 CPU(s):               0
Vulnerability Itlb multihit:     Not affected
Vulnerability L1tf:              Not affected
Vulnerability Mds:               Not affected
Vulnerability Meltdown:          Not affected
Vulnerability Spec store bypass: Mitigation; Speculative Store Bypass disabled via prctl
Vulnerability Spectre v1:        Mitigation; __user pointer sanitization
Vulnerability Spectre v2:        Not affected
Vulnerability Srbds:             Not affected
Vulnerability Tsx async abort:   Not affected
Flags:                           fp asimd evtstrm aes pmull sha1 sha2 crc32 atomics fphp asimdhp cpuid asimdrdm lrcpc dcpop asimddp ssbs

# cat /proc/cpuinfo

processor       : 0
BogoMIPS        : 50.00
Features        : fp asimd evtstrm aes pmull sha1 sha2 crc32 atomics fphp asimdhp cpuid asimdrdm lrcpc dcpop asimddp ssbs
CPU implementer : 0x41
CPU architecture: 8
CPU variant     : 0x3
CPU part        : 0xd0c
CPU revision    : 1

@kissablemt
Copy link
Author

lscpu
Architecture: armv7l
Byte Order: Little Endian
CPU(s): 4
On-line CPU(s) list: 0-3
Thread(s) per core: 1
Core(s) per socket: 4
Socket(s): 1
Vendor ID: ARM
Model: 3
Model name: Cortex-A72
Stepping: r0p3
CPU max MHz: 1500.0000
CPU min MHz: 600.0000
BogoMIPS: 108.00
Flags: half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm crc32

cat /proc/cpuinfo
processor : 0
model name : ARMv7 Processor rev 3 (v7l)
BogoMIPS : 108.00
Features : half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm crc32
CPU implementer : 0x41
CPU architecture: 7
CPU variant : 0x0
CPU part : 0xd08
CPU revision : 3

processor : 1
model name : ARMv7 Processor rev 3 (v7l)
BogoMIPS : 108.00
Features : half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm crc32
CPU implementer : 0x41
CPU architecture: 7
CPU variant : 0x0
CPU part : 0xd08
CPU revision : 3

processor : 2
model name : ARMv7 Processor rev 3 (v7l)
BogoMIPS : 108.00
Features : half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm crc32
CPU implementer : 0x41
CPU architecture: 7
CPU variant : 0x0
CPU part : 0xd08
CPU revision : 3

processor : 3
model name : ARMv7 Processor rev 3 (v7l)
BogoMIPS : 108.00
Features : half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm crc32
CPU implementer : 0x41
CPU architecture: 7
CPU variant : 0x0
CPU part : 0xd08
CPU revision : 3

Hardware : BCM2711
Revision : c03111
Serial : 10000000244a543c
Model : Raspberry Pi 4 Model B Rev 1.1

@mzz2017
Copy link
Owner

mzz2017 commented Dec 8, 2021

请尝试该版本是否已修复:https://github.com/mzz2017/gg/actions/runs/1552478468

@kissablemt
Copy link
Author

请尝试该版本是否已修复:https://github.com/mzz2017/gg/actions/runs/1552478468

太感谢啦!!可以啦!!
另外想问问,如何使用socks5?
gg config node

socks5://127.0.0.1:1089

然后gg curl cip.cc

FATA[0000] GetDialer:unable to connect to the proxy node: connectivity test failed: Get "https://fonts.gstatic.com/generate_204": EOF

@mzz2017
Copy link
Owner

mzz2017 commented Dec 8, 2021

我稍后尝试一下

@mzz2017
Copy link
Owner

mzz2017 commented Dec 8, 2021

我这里没什么问题,如果节点没问题的话可能是不支持 UDP,试试添加 --noudp

@kissablemt
Copy link
Author

kissablemt commented Dec 8, 2021

我这里没什么问题,如果节点没问题的话可能是不支持 UDP,试试添加 --noudp

我这边试了,gg --noudp --node socks5://127.0.0.1:1089 curl cip.cc,有时成功,但大部分都是

curl: (52) Empty reply from server

或者

curl: (56) Recv failure: Connection reset by peer

但是gg --noudp --node socks5://192.168.0.111:1089 curl cip.cc,就是使用局域网另一台机子的socks就成功了,不太清楚什么问题哎

使用本机的socks也没问题,但是要使用公网ip。"127.0.0.1"和内网ip都不行。

@kissablemt
Copy link
Author

发现了,两次gg --noudp --node socks5://127.0.0.1:1089 curl cip.cc运行间隔比较短,就会出现问题

@kissablemt
Copy link
Author

[2021-12-08 16:29:01] [ERROR] 127.0.0.1:50624 unknown protocol
[2021-12-08 16:29:01] [INFO] 127.0.0.1:50624 disconnected, 0 bytes received, 0 bytes sent, lasted for 0 seconds

这是trojan的日志

@mzz2017
Copy link
Owner

mzz2017 commented Dec 8, 2021

这是trojan的日志

你是说你使用 socks5 接本地的 v2ray 出口按 trojan 发出去就会出现问题是吗,这是服务器端的日志还是?

发现了,两次gg --noudp --node socks5://127.0.0.1:1089 curl cip.cc运行间隔比较短,就会出现问题

我按照你的方法没有成功复现

@kissablemt
Copy link
Author

kissablemt commented Dec 8, 2021

这是trojan的日志

你是说你使用 socks5 接本地的 v2ray 出口按 trojan 发出去就会出现问题是吗,这是服务器端的日志还是?

发现了,两次gg --noudp --node socks5://127.0.0.1:1089 curl cip.cc运行间隔比较短,就会出现问题

我按照你的方法没有成功复现

我是开的https://github.com/trojan-gfw/trojan , 然后开放了本地端口为1089,直接socks连过去的。直接export测试过是可以的。
那个日志是trojan-gfw里client端的日志

@mzz2017
Copy link
Owner

mzz2017 commented Dec 8, 2021

@kissablemt 已找到原因,所引用的包 github.com/txthinking/socks5 在 Write 时没有使用缓存,而是逐字节发送 TCP 流,而 trojan-gfw/trojan 在读时也没有直接读够字节数,而是只读一次来判断。

https://github.com/txthinking/socks5/blob/e03c1217a50bd1363a2aaf58290da622256704fa/client_side.go#L26
https://github.com/trojan-gfw/trojan/blob/3e7bb9aecdc694f9bcae8d646fae395f773d60f8/src/session/clientsession.cpp#L138

感谢报告。果然偷懒引包是要出问题的。

@mzz2017
Copy link
Owner

mzz2017 commented Dec 10, 2021

已修复于 https://github.com/mzz2017/gg/releases/tag/v0.1.12

@kissablemt
Copy link
Author

非常感谢!!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants