Opened 13 years ago

Last modified 13 years ago

#29549 new defect

tcpproxy crashes — at Initial Version

Reported by: digitalrinaldo@… Owned by: macports-tickets@…
Priority: Normal Milestone:
Component: ports Version: 1.9.2
Keywords: Cc:
Port: tcpproxy

Description

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 (0)

Note: See TracTickets for help on using tickets.