Ethereal-dev: Re: [ethereal-dev] SIGSEGV in strlen() -> packet-smb.c:9023

Note: This archive is from the project's previous web site, ethereal.com. This list is no longer active.

Date Index Thread Index Other Months All Mailing Lists
Date Prev Date Next Thread Prev Thread Next
From: Florian Lohoff <flo@xxxxxxxxxx>
Date: Thu, 25 Nov 1999 15:12:54 +0100
On Thu, Nov 25, 1999 at 11:52:30AM +1000, Richard Sharpe wrote:
> Hi,
> 
> At 01:51 PM 11/25/99 +0100, Florian Lohoff <flo@xxxxxxxxxx> wrote:
> >
> >I have already seen a SIG 11 posting in strchr which seems
> >to be the same cause ...
> 
> Hmmm, I think we fixed the strchr problem.

This is the ethereal 0.7.8 release - Probably only fixed in CVS after
release ?

> >Program received signal SIGSEGV, Segmentation fault.
> >0x402c072f in strlen ()
> >(gdb) bt
> >#0  0x402c072f in strlen ()
> >#1  0x80cd058 in dissect_transact_params (pd=0x81dd380 "", offset=114, 
> >    fd=0x81fbe38, parent=0x0, tree=0x0, si={tid = 2048, uid = 2048, 
> >      mid = 9857, pid = 0, conversation = 0x82c4da8, request_val =
> 0x82d3d18}, 
> >    max_data=408, SMB_offset=58, errcode=0, dirn=0, DataOffset=64, 
> >    DataCount=344, ParameterOffset=56, ParameterCount=8, TransactName=0x0)
> >    at packet-smb.c:9023
> 
> OK. Looks like there was some \PIPE or \MAILSLOT transaction or some other,
> and I am expecting the TransactName is null. 
> 
> Do you have the dump accessible?

I can reproduce this easily - Out lan seems to be full
of this Frames :)

> I will have to post my tool that allows you to edit a trace file, so we can
> send just the frame that causes the problem.

I though that i could save only the frames selected with the filter
which would be a great idea - Write a filter and do a "save" or
"save as..." and only save "selected" frames ...

Flo
-- 
Florian Lohoff		flo@xxxxxxxxxx		      	+49-5241-470566
  ...  The failure can be random; however, when it does occur, it is
  catastrophic and is repeatable  ...             Cisco Field Notice