SylvainTI / ostinato

Automatically exported from code.google.com/p/ostinato
GNU General Public License v3.0
0 stars 0 forks source link

Closing Stream Dialog causes segmentaion fault #5

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
When I am finished Editing a stream and click OK on the Edit Stream Dialog
the client crashes with the following output.  Any idea why?

DumpView::DumpView
loading mpStream 0xd2ea890
updateSelectProtocolsSimpleWidget
__updateProtocol: level = 0 old id = 0 new id = 0 upd? = 1
__updateProtocol: level = 1 old id = 0 new id = 0 upd? = 1
__updateProtocol: level = 2 old id = 0 new id = 0 upd? = 1
__updateProtocol: level = 3 old id = 0 new id = 0 upd? = 1
__updateProtocol: level = 4 old id = 0 new id = 0 upd? = 1
__updateProtocol: level = 5 old id = 0 new id = 0 upd? = 1
__updateProtocol: level = 6 old id = 0 new id = 0 upd? = 1
forceProtocolNone: chk? = 0, btn = 0xd2f64a0, L1 = 0xd2f64a0, L2 =
0xd3e3d60, L3 = 0xd307df0
disableProtocols: btnGrp = 0xd373920, chk? = 0
disableProtocols: btnGrp = 0xd3b68d0, chk? = 0
disableProtocols: btnGrp = 0xd37a670, chk? = 0
__updateProtocol: level = 0 old id = 0 new id = 51 upd? = 1
__updateProtocol: level = 6 old id = 0 new id = 52 upd? = 1
updateSelectProtocolsAdvancedWidget
0xd3164b0 -- 51
0xd3e17a0 -- 52
loading stream done
stream list activated

forceProtocolNone: chk? = 0, btn = 0xd3e3d60, L1 = 0xd2f64a0, L2 =
0xd3e3d60, L3 = 0xd307df0
disableProtocols: btnGrp = 0xd3782d0, chk? = 0
__updateProtocol: level = 2 old id = 0 new id = 121 upd? = 0
forceProtocolNone: chk? = 0, btn = 0xd307df0, L1 = 0xd2f64a0, L2 =
0xd3e3d60, L3 = 0xd307df0
disableProtocols: btnGrp = 0xd37a0f0, chk? = 0
__updateProtocol: level = 3 old id = 0 new id = 130 upd? = 0
forceProtocolNone: chk? = 0, btn = 0xd2ff870, L1 = 0xd2f64a0, L2 =
0xd3e3d60, L3 = 0xd307df0
disableProtocols: btnGrp = 0xd37a440, chk? = 0
__updateProtocol: level = 4 old id = 0 new id = 141 upd? = 0
storing pStream 0xd2ea890
payloadProtocolId: payloadProtocolId = 0x800
payloadProtocolId: payloadProtocolId = 0x0
payloadProtocolId: payloadProtocolId = 0x0
protocolFrameSize: protoSize = 8
protocolFrameSize: protoSize = 8
payloadProtocolId: payloadProtocolId = 0x11
protocolFrameSize: protoSize = 20
payloadProtocolId: payloadProtocolId = 0x800
protocolFrameSize: protoSize = 2
protocolFrameSize: protoSize = 12
protocolFrameOffset: ofs = 42
protocolFrameSize: this = 0xd3e17a0, streamIndex = 0, len = 18
protocolFramePayloadSize: payloadSize = 26
payloadProtocolId: payloadProtocolId = 0x11
<<< 0, 4/1 >>>>
<<< 1, 4/1 >>>>
<<< 1, 8/1 >>>>
protocolFrameSize: protoSize = 8
protocolFrameSize: protoSize = 8
protocolFrameSize: protoSize = 20
protocolFrameSize: protoSize = 2
protocolFrameSize: protoSize = 12
protocolFrameOffset: ofs = 42
protocolFrameSize: this = 0xd3e17a0, streamIndex = 0, len = 18
protocolFramePayloadSize: payloadSize = 26
<<< 2, 16/2 >>>>
<<< 4, 16/2 >>>>
<<< 6, 3/1 >>>>
<<< 7, 13/2 >>>>
<<< 8, 8/1 >>>>
payloadProtocolId: payloadProtocolId = 0x11
payloadProtocolId: payloadProtocolId = 0x11
<<< 9, 8/1 >>>>
<<< 10, 16/2 >>>>
<<< 12, 32/4 >>>>
<<< 16, 32/4 >>>>
payloadProtocolId: payloadProtocolId = 0x0
payloadProtocolId: payloadProtocolId = 0x0
protocolFrameSize: protoSize = 8
protocolFrameSize: protoSize = 20
protocolFrameSize: protoSize = 2
protocolFrameSize: protoSize = 12
protocolFrameOffset: ofs = 42
protocolFrameSize: this = 0xd3e17a0, streamIndex = 0, len = 18
protocolFramePayloadSize: payloadSize = 18
payloadProtocolId: payloadProtocolId = 0x0
payloadProtocolId: payloadProtocolId = 0x0
<<< 0, 16/2 >>>>
payloadProtocolId: payloadProtocolId = 0x0
payloadProtocolId: payloadProtocolId = 0x0
<<< 2, 16/2 >>>>
protocolFrameSize: protoSize = 8
protocolFrameSize: protoSize = 20
protocolFrameSize: protoSize = 2
protocolFrameSize: protoSize = 12
protocolFrameOffset: ofs = 42
protocolFrameSize: this = 0xd3e17a0, streamIndex = 0, len = 18
protocolFramePayloadSize: payloadSize = 18
<<< 4, 16/2 >>>>
<<< 6, 16/2 >>>>
protocolFrameSize: protoSize = 8
protocolFrameSize: protoSize = 20
protocolFrameSize: protoSize = 2
protocolFrameSize: protoSize = 12
protocolFrameOffset: ofs = 42
protocolFrameSize: this = 0xd3e17a0, streamIndex = 0, len = 18
protocolFrameSize: protoSize = 8
protocolFrameSize: protoSize = 20
protocolFrameSize: protoSize = 2
protocolFrameSize: protoSize = 12
protocolFrameOffset: ofs = 42
protocolFrameSize: this = 0xd3e17a0, streamIndex = 0, len = 18
<<< 0, 144/18 >>>>
payloadProtocolId: payloadProtocolId = 0x11
protocolFrameSize: protoSize = 8
protocolFrameSize: protoSize = 8
protocolFrameSize: protoSize = 20
protocolFrameSize: protoSize = 2
protocolFrameSize: protoSize = 12
protocolFrameOffset: ofs = 42
protocolFrameSize: this = 0xd3e17a0, streamIndex = 0, len = 18
protocolFramePayloadSize: payloadSize = 26
protocolFrameHeaderCksum: sum = 43, cksum = 65492
UDP cksum = 65466
protocolFrameSize: protoSize = 12
protocolFrameSize: protoSize = 2
protocolFrameSize: protoSize = 20
protocolFrameSize: protoSize = 8
protocolFrameSize: protoSize = 8
protocolFrameSize: protoSize = 20
protocolFrameSize: protoSize = 2
protocolFrameSize: protoSize = 12
protocolFrameOffset: ofs = 42
protocolFrameSize: this = 0xd3e17a0, streamIndex = 0, len = 18
stream stored
Segmentation fault
[root@localhost client]# 

Original issue reported on code.google.com by pjyoung...@gmail.com on 14 May 2010 at 9:02

GoogleCodeExporter commented 9 years ago
pjyoung311,

If you are using r59ec or ra140 revision of the code, please pull from the repo 
- I 
committed a fix for a similar problem in r78cd

If you are using the latest revision (r78cd as of this writing), then can you 
please 
provide the following information -
1. Does it happen everytime? With every stream?
2. List down all steps that you take while configuring the stream (protocol 
selection, changing protocol field values etc)
3. What version/revision of the code are you using?

Can you try running the client in gdb and send me the backtrace?

Please include any other relevant info that will help me in recreating the 
problem.

Regards,
Srivats

Original comment by pstav...@gmail.com on 15 May 2010 at 4:42

GoogleCodeExporter commented 9 years ago
It will be a couple of days before I can get in the lab to try this again.  But,
here's some more more info that I can offer quickly...

* I was using the latest revision as of yesterday (5/14/2010). 

* I'm running this on 64 bit CentOS.

* I would choose a port, create the stream, fill in a couple of protocols (Eth 
II,
IP, UDP) and fill in Ethernet and IP addresses and click OK.  This is where I 
got the
segfault.  I couldn't create the first stream.  I also tried just filling in the
protocols (without specifying adresses) with the same result.

It looks like you have made a good start to a very useful app here...

Original comment by pjyoung...@gmail.com on 15 May 2010 at 12:45

GoogleCodeExporter commented 9 years ago
This issue was closed by revision 332a921c0b.

Original comment by pstav...@gmail.com on 16 May 2010 at 6:17

GoogleCodeExporter commented 9 years ago
pjyoung311,

I've fixed the segfault. Please try again with r332a.

Srivats

Original comment by pstav...@gmail.com on 16 May 2010 at 6:20

GoogleCodeExporter commented 9 years ago
Yes, this is now fixed.

Original comment by pjyoung...@gmail.com on 17 May 2010 at 1:51

GoogleCodeExporter commented 9 years ago
@pjyoung311: Thanks for the confirmation and the words of encouragement :-)

Original comment by pstav...@gmail.com on 17 May 2010 at 3:22