Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Genplot causing segmentation or checksum error #119

Open
aaronmbr opened this issue Mar 31, 2015 · 3 comments
Open

Genplot causing segmentation or checksum error #119

aaronmbr opened this issue Mar 31, 2015 · 3 comments

Comments

@aaronmbr
Copy link
Contributor

Original issue 119 created by aaronmbr on 2014-02-10T12:26:23.000Z:

What steps will reproduce the problem?

  1. Running test with --snaplog or --cwnddecrease
  2. Using genplot or genplot10g

What is the expected output? What do you see instead?

  • Genplot will cause segmentation error
  • Genplot10g will cause Checksum error

What version of the product are you using? On what operating system?
Ubuntu Server 13.10
Linux 3.9 patched with web10g 2.0.7
Using current trunk

Please provide any additional information below.
I'm not quite sure if the problem is with the program or my testing, but I would be happy about any suggestion.

@aaronmbr
Copy link
Contributor Author

Comment #1 originally posted by aaronmbr on 2014-02-10T20:42:03.000Z:

Hi,

Thanks for reporting this issue. The segfault from genplot is easy to explain, genplot is intended to be used with Web100 snapshots so feeding it Web10G snapshots is causing this. Clearly this is not ideal behavior a warning would be a lot nicer, I'll look into the feasibility of detecting this.

As for the checksum error with genplot10g this seems to indicate some form of corruption or capture issue.
Is it possible for you to upload a copy of the snapshot that is causing this issue?

Thanks,

@aaronmbr
Copy link
Contributor Author

Comment #2 originally posted by aaronmbr on 2014-02-13T04:53:20.000Z:

Hello,
thank you or your reply. I think I have figured out the problem. I think the compression was the problem, if I don't use compression it works. I guess it's related to that topic: https://code.google.com/p/ndt/issues/detail?id=36&colspec=ID%20Type%20Status%20Severity%20Milestone%20Priority%20Owner%20Summary
I have attached the file anyway in case it might help solving the problem.

Thanks,
Martin

@aaronmbr
Copy link
Contributor Author

Comment #3 originally posted by aaronmbr on 2014-06-25T08:33:51.000Z:

<empty>

@aaronmbr aaronmbr removed their assignment May 18, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant