Skip to content

panic: runtime error: invalid memory address or nil pointer dereference #171

Closed

Description

@M0dred

proxify -version

[INF] Current Version: 0.0.7

proxify

Run proxify after 10 seconds, crash and show the following error:

panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x30 pc=0xece49c]

goroutine 403 [running]:
github.com/projectdiscovery/proxify.(*Proxy).Run.func4(0x90?, 0x7f1ca1281848?)
        /root/go/pkg/mod/github.com/elazarl/goproxy@v0.0.0-20210110162100-a92cc753f88e/dispatcher.go:123 +0x1c
github.com/elazarl/goproxy.ReqConditionFunc.HandleReq(0x30?, 0xc00005fc00?, 0xc00052d7d0?)
        /root/go/pkg/mod/github.com/elazarl/goproxy@v0.0.0-20210110162100-a92cc753f88e/dispatcher.go:33 +0x22
github.com/elazarl/goproxy.(*ReqProxyConds).Do.func1(0xc00028c780?, 0x29?)
        /root/go/pkg/mod/github.com/elazarl/goproxy@v0.0.0-20210110162100-a92cc753f88e/dispatcher.go:212 +0xa6
github.com/elazarl/goproxy.FuncReqHandler.Handle(0x29?, 0x0?, 0x12c67e0?)
        /root/go/pkg/mod/github.com/elazarl/goproxy@v0.0.0-20210110162100-a92cc753f88e/actions.go:19 +0x22
github.com/elazarl/goproxy.(*ProxyHttpServer).filterRequest(0xc00028c780?, 0xc000ba4700, 0x0?)
        /root/go/pkg/mod/github.com/elazarl/goproxy@v0.0.0-20210110162100-a92cc753f88e/proxy.go:62 +0x82
github.com/elazarl/goproxy.(*ProxyHttpServer).handleHttps.func2()
        /root/go/pkg/mod/github.com/elazarl/goproxy@v0.0.0-20210110162100-a92cc753f88e/https.go:220 +0x6cb
created by github.com/elazarl/goproxy.(*ProxyHttpServer).handleHttps
        /root/go/pkg/mod/github.com/elazarl/goproxy@v0.0.0-20210110162100-a92cc753f88e/https.go:190 +0x4b1

Activity

  1. added
    Type: BugInconsistencies or issues which will cause an issue or problem for users or implementors.
    on Oct 18, 2022
  2. ehsandeep commented on Oct 19, 2022

    @ehsandeep
    Member

    @M0dred thank you for reporting this, do you have a complete command to share that you used to run proxify?

  3. added
    Type: QuestionA query or seeking clarification on parts of the spec. Probably doesn't need the attention of all.
    on Oct 20, 2022
  4. locked and limited conversation to collaborators on Nov 25, 2022
  5. converted this issue into a discussion #194 on Nov 25, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Priority: MediumThis issue may be useful, and needs some attention.Type: BugInconsistencies or issues which will cause an issue or problem for users or implementors.Type: QuestionA query or seeking clarification on parts of the spec. Probably doesn't need the attention of all.investigationinvestigation

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions