[valgrind] [Bug 390524] use of 0b prefix for binary constants

2018-03-05 Thread Jeff Frontz
https://bugs.kde.org/show_bug.cgi?id=390524 --- Comment #2 from Jeff Frontz --- Note -- the target application is in a regulated industry and the development environment has all been validated (i.e., changing-up to a later version of gcc isn't in the cards for quite a while). Would it

[valgrind] [Bug 390471] New: suppression by specification of source-file line number

2018-02-14 Thread Jeff Frontz
https://bugs.kde.org/show_bug.cgi?id=390471 Bug ID: 390471 Summary: suppression by specification of source-file line number Product: valgrind Version: 3.13.0 Platform: Other OS: Linux Status: UNC

[valgrind] [Bug 390524] New: use of 0b prefix for binary constants

2018-02-15 Thread Jeff Frontz
https://bugs.kde.org/show_bug.cgi?id=390524 Bug ID: 390524 Summary: use of 0b prefix for binary constants Product: valgrind Version: 3.14 SVN Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal

[valgrind] [Bug 390524] use of 0b prefix for binary constants

2018-02-15 Thread Jeff Frontz
https://bugs.kde.org/show_bug.cgi?id=390524 --- Comment #1 from Jeff Frontz --- Converting the constant to a simple 0x10 seems to make everything better (at least as far as compilation and running on x86 linux). -- You are receiving this mail because: You are watching all bug changes.

[valgrind] [Bug 390471] suppression by specification of source-file line number

2018-02-15 Thread Jeff Frontz
https://bugs.kde.org/show_bug.cgi?id=390471 --- Comment #4 from Jeff Frontz --- Created attachment 110691 --> https://bugs.kde.org/attachment.cgi?id=110691&action=edit Patch against 3.14.0 src & doc to implement/document suppression-by-file -- You are receiving this mail becau

[valgrind] [Bug 390471] suppression by specification of source-file line number

2018-02-15 Thread Jeff Frontz
https://bugs.kde.org/show_bug.cgi?id=390471 --- Comment #5 from Jeff Frontz --- I'm not sure what the protocol is for creating test cases (I can't seem to get them to work in my environment) but if someone can give me a pointer, I'll do my best to create something. I tested th

[valgrind] [Bug 390792] New: 'impossible' happened in dh_handle_noninsn_write()

2018-02-20 Thread Jeff Frontz
https://bugs.kde.org/show_bug.cgi?id=390792 Bug ID: 390792 Summary: 'impossible' happened in dh_handle_noninsn_write() Product: valgrind Version: 3.14 SVN Platform: Compiled Sources OS: Linux Status: UNCONFIRMED

[valgrind] [Bug 390792] 'impossible' happened in dh_handle_noninsn_write()

2018-02-20 Thread Jeff Frontz
https://bugs.kde.org/show_bug.cgi?id=390792 --- Comment #1 from Jeff Frontz --- I changed the tl_assert(0) in dh_handle_noninsn_write() to print out the unhandled value (a la 'tl_assert2(0, "part is %d", part);'): DHAT: dh_main.c:756 (dh_handle_noninsn_write): the 'i