Wireshark · Wireshark-bugs: [Wireshark-bugs] [Bug 2162] for() loop evaluation order in ep

Wireshark-bugs: [Wireshark-bugs] [Bug 2162] for() loop evaluation order in ep_strndup() can trig

Date: Mon, 7 Jan 2008 18:17:49 +0000 (GMT)

http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=2162





------- Comment #9 from jyoung@xxxxxxx  2008-01-07 18:17 GMT -------
Hello Jeff/Japp, 

Could either one of you check this patch in?  

The patch applied for bug 2169 fixed the defect that ultimately triggered this
bug (bug 2162).  While this bug is now less likely to be triggered, I still
believe that this patch should be applied.

Thanks.


-- 
Configure bugmail: http://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

References:
- [Wireshark-bugs] [Bug 2162] New: for() loop evaluation order in ep_strndup() can trigger valgrind "invalid read of size 1"
  - From: bugzilla-daemon

Prev by Date: [Wireshark-bugs] [Bug 2169] g_malloc0() call in uat_unesc() (epan/uat.c) is one byte too short
Next by Date: [Wireshark-bugs] [Bug 2162] for() loop evaluation order in ep_strndup() can trigger valgrind "invalid read of size 1"
Previous by thread: [Wireshark-bugs] [Bug 2162] for() loop evaluation order in ep_strndup() can trigger valgrind "invalid read of size 1"
Next by thread: [Wireshark-bugs] [Bug 2162] for() loop evaluation order in ep_strndup() can trigger valgrind "invalid read of size 1"
Index(es):
- Date
- Thread