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: Fri, 4 Jan 2008 15:54:09 +0000 (GMT)

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





------- Comment #5 from jeff.morriss@xxxxxxxxxxx  2008-01-04 15:54 GMT -------
The patch makes sense to me, but:

Should the caller be using a string duplication function on something that's
not a (proper) string?  (In other words is there another bug there?)  I took a
quick look and couldn't quite figure out what's going on there.


-- 
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 2164] Packet dissector showing bogus errors in jabber packets
Next by Date: [Wireshark-bugs] [Bug 2165] New: Regression on decoding H248
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