[MacPorts] #13908: Wireshark bombs when capturing data (x11 shuts down) MACBook pro OSX 10.5.1

MacPorts trac at macosforge.org
Sun Jan 13 16:15:15 PST 2008


#13908: Wireshark bombs when capturing data (x11 shuts down) MACBook pro OSX 10.5.1
---------------------------------+------------------------------------------
  Reporter:  p.ramsey at gmail.com  |       Owner:  macports-tickets at lists.macosforge.org
      Type:  defect              |      Status:  new                                  
  Priority:  Normal              |   Milestone:  Port Bugs                            
 Component:  ports               |     Version:  1.6.0                                
Resolution:                      |    Keywords:  wireshark, x11, crashes, badmatch    
---------------------------------+------------------------------------------
Changes (by jmpp at macports.org):

  * milestone:  => Port Bugs

Old description:

> Capturing on en1 (which is wireless)
>
> bash-3.2$ sudo ./wireshark
> The program 'wireshark' received an X Window System error.
> This probably reflects a bug in the program.
> The error was 'BadMatch (invalid parameter attributes)'.
>   (Details: serial 11864 error_code 8 request_code 152 minor_code 4)
>   (Note to programmers: normally, X errors are reported asynchronously;
>    that is, you will receive the error a while after causing it.
>    To debug your program, run it with the --sync command line
>    option to change this behavior. You can then get a meaningful
>    backtrace from your debugger if you break on the gdk_x_error()
> function.)

New description:

 Capturing on en1 (which is wireless)

 {{{
 bash-3.2$ sudo ./wireshark
 The program 'wireshark' received an X Window System error.
 This probably reflects a bug in the program.
 The error was 'BadMatch (invalid parameter attributes)'.
   (Details: serial 11864 error_code 8 request_code 152 minor_code 4)
   (Note to programmers: normally, X errors are reported asynchronously;
    that is, you will receive the error a while after causing it.
    To debug your program, run it with the --sync command line
    option to change this behavior. You can then get a meaningful
    backtrace from your debugger if you break on the gdk_x_error()
 function.)
 }}}

-- 
Ticket URL: <http://trac.macosforge.org/projects/macports/ticket/13908#comment:1>
MacPorts </projects/macports>
Ports system for Mac OS


More information about the macports-tickets mailing list