Opened 13 years ago
Last modified 13 years ago
#29549 new defect
tcpproxy crashes
| Reported by: | digitalrinaldo@… | Owned by: | macports-tickets@… |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | 1.9.2 |
| Keywords: | Cc: | ryandesign (Ryan Carsten Schmidt) | |
| Port: | tcpproxy |
Description (last modified by ryandesign (Ryan Carsten Schmidt))
Process: tcpproxy [78886]
Path: /opt/local/sbin/tcpproxy
Identifier: tcpproxy
Version: ??? (???)
Code Type: X86-64 (Native)
Parent Process: tcpproxy [78829]
Date/Time: 2011-05-22 09:55:01.107 -0400
OS Version: Mac OS X 10.6.7 (10J869)
Report Version: 6
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000070926600
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Thread 0 Crashed: Dispatch queue: com.apple.main-thread
0 tcpproxy 0x00000001000044c3 0x100000000 + 17603
1 tcpproxy 0x00000001000047d2 0x100000000 + 18386
2 tcpproxy 0x0000000100001109 0x100000000 + 4361
3 tcpproxy 0x00000001000034ad 0x100000000 + 13485
4 tcpproxy 0x0000000100000ee4 0x100000000 + 3812
Thread 0 crashed with X86 Thread State (64-bit):
rax: 0x00007fff70926600 rbx: 0x000000000000012c rcx: 0x0000000000000000 rdx: 0x000000000000012c
rdi: 0x0000000070926600 rsi: 0x0000000070926600 rbp: 0x00007fff5fbff5d0 rsp: 0x00007fff5fbff5d0
r8: 0x00007fff5fbff380 r9: 0x0000000000000000 r10: 0x00007fff85d4279a r11: 0x00007fff70926600
r12: 0x000000000000012c r13: 0x00007fff5fbff7e0 r14: 0x0000000000000034 r15: 0x0000000000000001
rip: 0x00000001000044c3 rfl: 0x0000000000010202 cr2: 0x0000000070926600
Binary Images:
0x100000000 - 0x100005ff7 +tcpproxy ??? (???) <8AF60E0F-B43A-26CF-AD5B-BE364AF4DF75> /opt/local/sbin/tcpproxy
0x7fff5fc00000 - 0x7fff5fc3bdef dyld 132.1 (???) <B536F2F1-9DF1-3B6C-1C2C-9075EA219A06> /usr/lib/dyld
0x7fff84698000 - 0x7fff8469cff7 libmathCommon.A.dylib 315.0.0 (compatibility 1.0.0) <95718673-FEEE-B6ED-B127-BCDBDB60D4E5> /usr/lib/system/libmathCommon.A.dylib
0x7fff85bfb000 - 0x7fff85dbcfff libSystem.B.dylib 125.2.10 (compatibility 1.0.0) <9BAEB2F2-B485-6349-E1AB-637FE12EE770> /usr/lib/libSystem.B.dylib
Change History (6)
comment:1 Changed 13 years ago by ryandesign (Ryan Carsten Schmidt)
| Description: | modified (diff) |
|---|---|
| Port: | tcpproxy added |
comment:2 Changed 13 years ago by ryandesign (Ryan Carsten Schmidt)
I tried updating the port to 2.0.0-beta15, but am stumped at:
tcpproxy.c:48:34: error: linux/netfilter_ipv4.h: No such file or directory
Obviously, Mac OS X doesn't have any headers in directories called "linux" and I'm not sure if there is an equivalent of this header on Mac OS X.
comment:3 Changed 13 years ago by ryandesign (Ryan Carsten Schmidt)
Looks like an update to 2.0.0-beta15 was submitted once before in #16324; I'll reopen that ticket and handle the update there.
comment:4 Changed 13 years ago by ryandesign (Ryan Carsten Schmidt)
| Cc: | ryandesign@… added |
|---|
The port is updated to 2.0.0-beta15 now. Please let us know here whether it still crashes.
comment:5 Changed 13 years ago by digitalrinaldo@…
I just updated to the 2.0.0.-beta15 version
The config I was using wih the previous version is no longer considered a valid file by the current version
May 23 07:05:11 m1 tcpproxy[28572]: -ERR: trailing characters: server imap.gmail.com:993, parameter= interface, /opt/local/etc/tcpproxy.conf:2
port 9900 interface localhost server imap.gmail.com:993 port 9901 interface localhost server smtp.gmail.com:465 port 9902 interface localhost server plus.pop.mail.yahoo.com:995 port 9903 interface localhost server smtp.pop.mail.yahoo.com:465
comment:6 Changed 13 years ago by ryandesign (Ryan Carsten Schmidt)
I'm afraid I don't know tcpproxy or how its config file syntax could be. Can you investigate?
It doesn't crash for me, but I just created an empty tcpproxy.conf file (since it didn't start without it). Perhaps the crash depends on your config options. What's in your tcpproxy.conf? Can you tell us anything else about what triggers the crash?
Perhaps we should update the port to version 2.0.0-beta15. Normally we wouldn't update ports to unstable versions, but the old 1.1.9 version isn't even available on the developer's web site anymore, and 2.0.0-beta15 is listed there as the "current" version, and has been since September 2007.