[krita] [Bug 391025] overwriting a brush setting remove the tags of the brush

2018-08-11 Thread Julian
https://bugs.kde.org/show_bug.cgi?id=391025 Julian changed: What|Removed |Added CC||juliando...@googlemail.com --- Comment #7 from Julian

[plasmashell] [Bug 413226] New: Plasma crashed after applying settings for wallpaper slideshow

2019-10-20 Thread Julian
https://bugs.kde.org/show_bug.cgi?id=413226 Bug ID: 413226 Summary: Plasma crashed after applying settings for wallpaper slideshow Product: plasmashell Version: 5.17.0 Platform: openSUSE RPMs OS: Linux

[gwenview] [Bug 414631] gwenview crashes with output "Floating point exception (core dumped)"

2019-11-28 Thread Julian
https://bugs.kde.org/show_bug.cgi?id=414631 Julian changed: What|Removed |Added CC||ju-0...@gmx.ch -- You are receiving this mail

[gwenview] [Bug 414631] New: gwenview crashes with output "Floating point exception (core dumped)"

2019-11-28 Thread Julian
https://bugs.kde.org/show_bug.cgi?id=414631 Bug ID: 414631 Summary: gwenview crashes with output "Floating point exception (core dumped)" Product: gwenview Version: 19.08.3 Platform: Manjaro OS: Linux

[gwenview] [Bug 414631] gwenview crashes with output "Floating point exception (core dumped)"

2019-11-28 Thread Julian
https://bugs.kde.org/show_bug.cgi?id=414631 --- Comment #1 from Julian --- The problem only occurs when the Thumbnail Bar is activated. -- You are receiving this mail because: You are watching all bug changes.

[gwenview] [Bug 414631] gwenview crashes with output "Floating point exception (core dumped)"

2019-12-20 Thread Julian
https://bugs.kde.org/show_bug.cgi?id=414631 --- Comment #3 from Julian --- Created attachment 124626 --> https://bugs.kde.org/attachment.cgi?id=124626=edit Crash report / backtrace on KDE Neon Developer Edition -- You are receiving this mail because: You are watching all bug changes.

[gwenview] [Bug 414631] gwenview crashes with output "Floating point exception (core dumped)"

2019-12-20 Thread Julian
https://bugs.kde.org/show_bug.cgi?id=414631 Julian changed: What|Removed |Added Attachment #124626|0 |1 is obsolete

[gwenview] [Bug 414631] gwenview crashes with output "Floating point exception (core dumped)"

2019-12-20 Thread Julian
https://bugs.kde.org/show_bug.cgi?id=414631 Julian changed: What|Removed |Added Attachment #124627|Crash report / backtrace on |Crash report / backtrace on description|KDE

[gwenview] [Bug 414631] gwenview crashes with output "Floating point exception (core dumped)"

2019-12-20 Thread Julian
https://bugs.kde.org/show_bug.cgi?id=414631 --- Comment #4 from Julian --- (In reply to Christoph Feck from comment #2) > If this is reproducible, could you add the backtrace for the crash? For more > information, please read > https://community.kde.org/Guidelines_and_HOWTOs/

[okular] [Bug 434595] New: Documents always open in new window

2021-03-18 Thread Julian
https://bugs.kde.org/show_bug.cgi?id=434595 Bug ID: 434595 Summary: Documents always open in new window Product: okular Version: 20.12.3 Platform: Snap OS: Linux Status: REPORTED Severity: normal

[neon] [Bug 434595] Okular: documents always open in new window

2021-03-18 Thread Julian
https://bugs.kde.org/show_bug.cgi?id=434595 --- Comment #1 from Julian --- I just installed lastest/edge via ```snap install okular --edge``` where everything works as expected. -- You are receiving this mail because: You are watching all bug changes.

[okular] [Bug 432942] New: Same document opens in new window/tag

2021-02-14 Thread Julian
https://bugs.kde.org/show_bug.cgi?id=432942 Bug ID: 432942 Summary: Same document opens in new window/tag Product: okular Version: unspecified Platform: Ubuntu Packages OS: Linux Status: REPORTED

[Spectacle] [Bug 475865] New: Spectacle traps you in rectangle screenshot mode if you try to take screenshot of Citrix session window

2023-10-20 Thread Julian
https://bugs.kde.org/show_bug.cgi?id=475865 Bug ID: 475865 Summary: Spectacle traps you in rectangle screenshot mode if you try to take screenshot of Citrix session window Classification: Applications Product: Spectacle Version:

[krita] [Bug 456774] New: No animation :(

2022-07-15 Thread Julian
https://bugs.kde.org/show_bug.cgi?id=456774 Bug ID: 456774 Summary: No animation :( Product: krita Version: unspecified Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR

[okular] [Bug 457245] Tablet or touchscreen-friendly settings

2022-07-28 Thread Julian
https://bugs.kde.org/show_bug.cgi?id=457245 --- Comment #1 from Julian --- Edit: version is 1.10.70, could not find that in the drop down menu. -- You are receiving this mail because: You are watching all bug changes.

[okular] [Bug 457245] New: Tablet or touchscreen-friendly settings

2022-07-28 Thread Julian
https://bugs.kde.org/show_bug.cgi?id=457245 Bug ID: 457245 Summary: Tablet or touchscreen-friendly settings Product: okular Version: unspecified Platform: unspecified OS: Linux Status: REPORTED Severity:

[okular] [Bug 457274] Option to turn off pinch controls for zoom

2022-07-29 Thread Julian
https://bugs.kde.org/show_bug.cgi?id=457274 --- Comment #1 from Julian --- Edit: Version is 1.10 or 20.04, but that version is not available in the drop-down menu at the moment. -- You are receiving this mail because: You are watching all bug changes.

[okular] [Bug 457245] Tablet or touchscreen-friendly settings

2022-07-29 Thread Julian
https://bugs.kde.org/show_bug.cgi?id=457245 --- Comment #3 from Julian --- 1. Glad to hear that scrolling is fixed. 2. Yes, turning off the pinch gesture is what I had in mind. One could imagine some more fine grained control options regarding when zoom gets actuated, but that might hardly

[okular] [Bug 457245] Tablet or touchscreen-friendly settings

2022-07-29 Thread Julian
https://bugs.kde.org/show_bug.cgi?id=457245 --- Comment #4 from Julian --- Missed your last paragraph, I will open two bug reports for the two requests. -- You are receiving this mail because: You are watching all bug changes.

[okular] [Bug 457274] New: Option to turn off pinch controls for zoom

2022-07-29 Thread Julian
https://bugs.kde.org/show_bug.cgi?id=457274 Bug ID: 457274 Summary: Option to turn off pinch controls for zoom Product: okular Version: unspecified Platform: Ubuntu Packages OS: Linux Status: REPORTED

[okular] [Bug 457275] New: Inline note resize box size

2022-07-29 Thread Julian
https://bugs.kde.org/show_bug.cgi?id=457275 Bug ID: 457275 Summary: Inline note resize box size Product: okular Version: unspecified Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: wishlist

[plasmashell] [Bug 460048] New: Editing Plasma panel crashes plasma

2022-10-06 Thread Julian
https://bugs.kde.org/show_bug.cgi?id=460048 Bug ID: 460048 Summary: Editing Plasma panel crashes plasma Classification: Plasma Product: plasmashell Version: 5.25.5 Platform: Neon OS: Linux Status: REPORTED

[kde] [Bug 460168] New: No puedo hacer que arranque Digikam 7.8.0.0

2022-10-09 Thread Julian
https://bugs.kde.org/show_bug.cgi?id=460168 Bug ID: 460168 Summary: No puedo hacer que arranque Digikam 7.8.0.0 Classification: I don't know Product: kde Version: unspecified Platform: Microsoft Windows OS: Microsoft

[kde] [Bug 460168] No puedo hacer que arranque Digikam 7.8.0.0

2022-10-09 Thread Julian
https://bugs.kde.org/show_bug.cgi?id=460168 --- Comment #1 from Julian --- Comment on attachment 152667 --> https://bugs.kde.org/attachment.cgi?id=152667 Esto es lo que dice No tiene suficientes privilegios es la base de datos. No tiene asignados los privilegios siguientes: CREATE TA

[kde] [Bug 460168] No puedo hacer que arranque Digikam 7.8.0.0

2022-10-09 Thread Julian
https://bugs.kde.org/show_bug.cgi?id=460168 Julian changed: What|Removed |Added CC||juliangem...@gmail.com -- You are receiving

[kdevelop] [Bug 460466] New: Dark theming broken on popups

2022-10-15 Thread Julian
https://bugs.kde.org/show_bug.cgi?id=460466 Bug ID: 460466 Summary: Dark theming broken on popups Classification: Applications Product: kdevelop Version: 5.9.220801 Platform: Fedora RPMs OS: Linux Status:

[kdevelop] [Bug 460465] New: Theming (dark) is broken on Windows

2022-10-15 Thread Julian
https://bugs.kde.org/show_bug.cgi?id=460465 Bug ID: 460465 Summary: Theming (dark) is broken on Windows Classification: Applications Product: kdevelop Version: 5.5.0 Platform: Other OS: Microsoft Windows

[krunner] [Bug 470622] New: Krunner runs/starts whatever is currently highlighted when pressing return, but it should finish the search and then run/start

2023-06-04 Thread Julian
https://bugs.kde.org/show_bug.cgi?id=470622 Bug ID: 470622 Summary: Krunner runs/starts whatever is currently highlighted when pressing return, but it should finish the search and then run/start Classification: Plasma

[dolphin] [Bug 471016] New: MTP merge directories not working

2023-06-14 Thread Julian
https://bugs.kde.org/show_bug.cgi?id=471016 Bug ID: 471016 Summary: MTP merge directories not working Classification: Applications Product: dolphin Version: 23.04.2 Platform: Fedora RPMs OS: Linux Status:

[okular] [Bug 471158] New: Add a way to permanently silence "This document has forms" dialogue

2023-06-17 Thread Julian
https://bugs.kde.org/show_bug.cgi?id=471158 Bug ID: 471158 Summary: Add a way to permanently silence "This document has forms" dialogue Classification: Applications Product: okular Version: 21.12.3 Platform: Ubuntu

[kde] [Bug 480000] New: Scaling of Jetbrains IDEs broken since updates

2024-01-18 Thread Julian
https://bugs.kde.org/show_bug.cgi?id=48 Bug ID: 48 Summary: Scaling of Jetbrains IDEs broken since updates Classification: I don't know Product: kde Version: unspecified Platform: Other OS: Linux

[kde] [Bug 479998] New: All apps crash on docking station connect if dbeaver is running

2024-01-18 Thread Julian
https://bugs.kde.org/show_bug.cgi?id=479998 Bug ID: 479998 Summary: All apps crash on docking station connect if dbeaver is running Classification: I don't know Product: kde Version: unspecified Platform: Other

[ghostwriter] [Bug 480055] New: Allow setting flags for pandoc or using custom command

2024-01-19 Thread Julian
https://bugs.kde.org/show_bug.cgi?id=480055 Bug ID: 480055 Summary: Allow setting flags for pandoc or using custom command Classification: Applications Product: ghostwriter Version: unspecified Platform: Debian stable OS:

[plasmashell] [Bug 487120] New: NVIDIA 3080, proprietary drivers with Wayland constant crashes plasma 6

2024-05-16 Thread Julian
https://bugs.kde.org/show_bug.cgi?id=487120 Bug ID: 487120 Summary: NVIDIA 3080, proprietary drivers with Wayland constant crashes plasma 6 Classification: Plasma Product: plasmashell Version: 6.0.4 Platform: Arch

[plasmashell] [Bug 487120] NVIDIA 3080, proprietary drivers with Wayland constant crashes plasma 6

2024-05-16 Thread Julian
https://bugs.kde.org/show_bug.cgi?id=487120 --- Comment #1 from Julian --- crash in action: https://youtu.be/HYeuXPCncC8 -- You are receiving this mail because: You are watching all bug changes.

[kde] [Bug 479998] All apps crash on docking station connect if dbeaver is running

2024-03-01 Thread Julian
https://bugs.kde.org/show_bug.cgi?id=479998 --- Comment #3 from Julian --- I don't know if plasma crashes, what i see is that every application is gone. -- You are receiving this mail because: You are watching all bug changes.

[valgrind] [Bug 303877] valgrind doesn't support compressed debuginfo sections.

2016-01-31 Thread julian-kde
https://bugs.kde.org/show_bug.cgi?id=303877 julian-...@d-and-j.net <julian-...@d-and-j.net> changed: What|Removed |Added CC| |julian

[valgrind] [Bug 358620] ARM: disInstr(arm): unhandled instruction: 0xF1010200

2017-02-01 Thread Julian Seward
https://bugs.kde.org/show_bug.cgi?id=358620 --- Comment #12 from Julian Seward <jsew...@acm.org> --- See https://bugs.kde.org/show_bug.cgi?id=322935#c27 and the comments that follow. -- You are receiving this mail because: You are watching all bug changes.

[valgrind] [Bug 374940] i386: Stack access at -1(%%esp)

2017-01-22 Thread Julian Seward
https://bugs.kde.org/show_bug.cgi?id=374940 Julian Seward <jsew...@acm.org> changed: What|Removed |Added Resolution|--- |INVALID

[valgrind] [Bug 374940] i386: Stack access at -1(%%esp)

2017-01-23 Thread Julian Seward
https://bugs.kde.org/show_bug.cgi?id=374940 --- Comment #7 from Julian Seward <jsew...@acm.org> --- FWIW, the ppc32-elf ABI says Data in the stack segment at addresses below the stack pointer contain undefined values. The ppc64-elf ABI says As discussed later in this chapter, the

[valgrind] [Bug 374940] i386: Stack access at -1(%%esp)

2017-01-23 Thread Julian Seward
https://bugs.kde.org/show_bug.cgi?id=374940 --- Comment #6 from Julian Seward <jsew...@acm.org> --- (In reply to Matthias Urlichs from comment #4) > * the kernel needs to handle negative %esp offsets all the time because when > you grow the stack the kernel "sees" th

[valgrind] [Bug 375171] Crash when running "hello world"

2017-01-17 Thread Julian Seward
https://bugs.kde.org/show_bug.cgi?id=375171 --- Comment #8 from Julian Seward <jsew...@acm.org> --- (In reply to Patrik Nyberg from comment #5) Are you sure that the i5-6200U connection is the only thing in common? That processor is a mid-range Skylake, and I am sure we would have heard

[valgrind] [Bug 375171] Crash when running "hello world"

2017-01-17 Thread Julian Seward
https://bugs.kde.org/show_bug.cgi?id=375171 --- Comment #4 from Julian Seward <jsew...@acm.org> --- I don't have any such problems with the 4.9.3 kernel that comes with Fedora 25. Is it possible that this is a Gentoo-specific problem? -- You are receiving this mail because: You are wa

[valgrind] [Bug 375171] Crash when running "hello world"

2017-01-17 Thread Julian Seward
https://bugs.kde.org/show_bug.cgi?id=375171 --- Comment #7 from Julian Seward <jsew...@acm.org> --- (In reply to Patrik Nyberg from comment #6) > This patch will solve the problem (at least for the simple hello world case). Sure. That just disables the assertion, though. It doesn'

[valgrind] [Bug 375171] Crash when running "hello world"

2017-01-17 Thread Julian Seward
https://bugs.kde.org/show_bug.cgi?id=375171 --- Comment #2 from Julian Seward <jsew...@acm.org> --- (In reply to Patrik Nyberg from comment #1) > Downgrading kernel to version 4.4.39-gentoo and the error is no longer > present. Yeah, I did wonder if this is kernel specific. The

[valgrind] [Bug 344139] vex x86->IR: unhandled instruction bytes: 0x36 0x8A 0x18 0x22 (and many other examples)

2017-01-20 Thread Julian Seward
https://bugs.kde.org/show_bug.cgi?id=344139 --- Comment #5 from Julian Seward <jsew...@acm.org> --- > Created attachment 103551 [details] > [PATCH 1/2] Initialize x86 system GDT on first use. Committed, valgrind r16204. > Created attachment 103552 [details] > [PATCH 2/2] VEX

[valgrind] [Bug 374850] The Impossible Happened

2017-01-19 Thread Julian Seward
https://bugs.kde.org/show_bug.cgi?id=374850 --- Comment #5 from Julian Seward <jsew...@acm.org> --- Oh, wait. This got discussed the other day. The conclusion is that it is basically a kernel bug that only manifests on Skylake processors. Are you running on Skylake? -- You are rec

[valgrind] [Bug 344139] vex x86->IR: unhandled instruction bytes: 0x36 0x8A 0x18 0x22 (and many other examples)

2017-01-20 Thread Julian Seward
https://bugs.kde.org/show_bug.cgi?id=344139 --- Comment #6 from Julian Seward <jsew...@acm.org> --- Richard .. 2 years later .. can we close this now? -- You are receiving this mail because: You are watching all bug changes.

[valgrind] [Bug 372120] c++ demangler demangles symbols which are not c++

2016-11-07 Thread Julian Seward
https://bugs.kde.org/show_bug.cgi?id=372120 --- Comment #2 from Julian Seward <jsew...@acm.org> --- (In reply to Mark Wielaard from comment #1) > Yeah, I think it would be a good idea to at least recognize the > default (gnu_v3) style c++ mangling, which always starts with _Z. >

[valgrind] [Bug 371916] execution tree xtree concept

2016-11-10 Thread Julian Seward
https://bugs.kde.org/show_bug.cgi?id=371916 --- Comment #18 from Julian Seward <jsew...@acm.org> --- Some comments on the v3 patch: Mostly it looks fine. Below [1] some small comments. Larger comments: * I assume there are no regressions with correctness or performance with thi

[valgrind] [Bug 352767] Wine/valgrind: Warning: noted but unhandled ioctl 0x5307 with no size/direction hints. (CDROMSTOP)

2016-11-23 Thread Julian Seward
https://bugs.kde.org/show_bug.cgi?id=352767 Julian Seward <jsew...@acm.org> changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Reso

[valgrind] [Bug 348616] Wine/valgrind: Warning: noted but unhandled ioctl 0x5390 with no size/direction hints. (DVD_READ_STRUCT)

2016-11-23 Thread Julian Seward
https://bugs.kde.org/show_bug.cgi?id=348616 Julian Seward <jsew...@acm.org> changed: What|Removed |Added Resolution|--- |FIXED

[valgrind] [Bug 371966] No uninitialised values reported with PGI -Mstack_arrays

2016-11-22 Thread Julian Seward
https://bugs.kde.org/show_bug.cgi?id=371966 --- Comment #12 from Julian Seward <jsew...@acm.org> --- Probably your least-worst option at this point is to compile the test program in the configuration where the errors are not reported, and hope that it all gets compiled into a single fu

[valgrind] [Bug 369459] valgrind on arm64 violates the ARMv8 spec (ldxr/stxr)

2016-11-24 Thread Julian Seward
https://bugs.kde.org/show_bug.cgi?id=369459 --- Comment #16 from Julian Seward <jsew...@acm.org> --- I would be happy to make a generalised version of Maran's fixes, so as to get arm{32,64} working on these cores. I don't really want it to be the default implementation though, since w

[valgrind] [Bug 372794] LibVEX 'Assertion szBlg2 <= 3'

2016-11-25 Thread Julian Seward
https://bugs.kde.org/show_bug.cgi?id=372794 --- Comment #1 from Julian Seward <jsew...@acm.org> --- Ach, the logic there that verifies whether the instruction decode is valid, is wrong. Try this: change // Paranoia .. vassert(szBlg2 <= 3); if (szBlg2 < 3) { vasse

[valgrind] [Bug 372358] vex amd64->IR: unhandled instruction bytes: 0xC5 0xFA 0x7F 0x45 0x80 0xC5 0xFA 0x7F 0x4D 0x90

2016-11-25 Thread Julian Seward
https://bugs.kde.org/show_bug.cgi?id=372358 --- Comment #2 from Julian Seward <jsew...@acm.org> --- I can't reproduce this. Are you sure this is right? I tried thusly: int main ( void ) { __asm__ __volatile__( ".byte 0xC5, 0xFA, 0x7F, 0x45, 0x80, 0xC5, 0xFA, 0x7F, 0x4D, 0x90

[valgrind] [Bug 371989] PCMPISTRM $0x72 and PCMPISTRI $0x12 validity bit propagation is imprecise

2016-11-25 Thread Julian Seward
https://bugs.kde.org/show_bug.cgi?id=371989 --- Comment #4 from Julian Seward <jsew...@acm.org> --- I'd fix this, if I could think of a sane way to do so. Alas .. -- You are receiving this mail because: You are watching all bug changes.

[valgrind] [Bug 372358] vex amd64->IR: unhandled instruction bytes: 0xC5 0xFA 0x7F 0x45 0x80 0xC5 0xFA 0x7F 0x4D 0x90

2016-11-25 Thread Julian Seward
https://bugs.kde.org/show_bug.cgi?id=372358 --- Comment #4 from Julian Seward <jsew...@acm.org> --- Are you running this test on a machine whose CPUID says that AVX isn't supported? Does the test actually run natively on the machine? I'm pretty sure VEX will decline to decode th

[frameworks-baloo] [Bug 372655] Baloo crash

2016-11-21 Thread Julian Schmidt
https://bugs.kde.org/show_bug.cgi?id=372655 --- Comment #1 from Julian Schmidt <jul...@chipmusik.de> --- the crash also happens when I copy/create a file with dolphin. Seems like a general HD access problem. -- You are receiving this mail because: You are watching all bug changes.

[kde] [Bug 372655] New: Baloo crash

2016-11-19 Thread Julian Schmidt
https://bugs.kde.org/show_bug.cgi?id=372655 Bug ID: 372655 Summary: Baloo crash Product: kde Version: unspecified Platform: unspecified OS: Linux Status: UNCONFIRMED Keywords: drkonqi Severity:

[valgrind] [Bug 372794] LibVEX 'Assertion szBlg2 <= 3'

2017-01-10 Thread Julian Seward
https://bugs.kde.org/show_bug.cgi?id=372794 Julian Seward <jsew...@acm.org> changed: What|Removed |Added Resolution|--- |FIXED

[valgrind] [Bug 374940] i386: Stack access at -1(%%esp)

2017-01-12 Thread Julian Seward
https://bugs.kde.org/show_bug.cgi?id=374940 --- Comment #3 from Julian Seward <jsew...@acm.org> --- The libev code is incorrect and should be fixed. It it violates the ABI. The problem isn't that the memory is uninitialised. It is that the program isn't allowed to access below %esp at an

[valgrind] [Bug 372794] LibVEX 'Assertion szBlg2 <= 3'

2017-01-13 Thread Julian Seward
https://bugs.kde.org/show_bug.cgi?id=372794 --- Comment #5 from Julian Seward <jsew...@acm.org> --- (In reply to Claus Strasburger from comment #4) > more -- this one is 0xFEBB0B40, VRINTM.f64), in code generated with > -mcpu=cortex-a53 -mfpu=neon-fp-armv8 (for the Raspberry Pi

[valgrind] [Bug 372794] LibVEX 'Assertion szBlg2 <= 3'

2017-01-13 Thread Julian Seward
https://bugs.kde.org/show_bug.cgi?id=372794 --- Comment #6 from Julian Seward <jsew...@acm.org> --- > all the instructions that "gcc-5.4 -mfpu=neon-fp-armv8". += "generates." -- You are receiving this mail because: You are watching all bug changes.

[valgrind] [Bug 371966] No uninitialised values reported with PGI -Mstack_arrays

2016-11-30 Thread Julian Seward
https://bugs.kde.org/show_bug.cgi?id=371966 --- Comment #23 from Julian Seward <jsew...@acm.org> --- (In reply to Carl Ponder from comment #22) > I know they're not zeroing out the space. That doesn't sync with my understanding of the discussion above. I think your chances o

[valgrind] [Bug 371966] No uninitialised values reported with PGI -Mstack_arrays

2016-11-30 Thread Julian Seward
https://bugs.kde.org/show_bug.cgi?id=371966 --- Comment #21 from Julian Seward <jsew...@acm.org> --- (In reply to Tom Hughes from comment #19) My assumption about what __builtin_aa does is: it moves RSP down by the specified amount, zeroes out the new area, and then returns. Except .. ho

[valgrind] [Bug 375839] Temporary storage exhusted , when long sequence of vfmadd231ps instructions to be executed

2017-03-27 Thread Julian Seward
https://bugs.kde.org/show_bug.cgi?id=375839 --- Comment #7 from Julian Seward <jsew...@acm.org> --- (In reply to Julian Seward from comment #1) > VEX has a very poor (verbose) translation for such instructions [..] VEX r3331 somewhat improves this, reducing the size of the gener

[valgrind] [Bug 375839] Temporary storage exhusted , when long sequence of vfmadd231ps instructions to be executed

2017-03-28 Thread Julian Seward
https://bugs.kde.org/show_bug.cgi?id=375839 --- Comment #8 from Julian Seward <jsew...@acm.org> --- VEX r3335 further improves the situation a bit. I would be interested to hear if this makes it possible to run these problematic cases without the workaround in comment #4 (the use of --vex

[valgrind] [Bug 358697] valgrind.h: Some code remains even when defining NVALGRIND

2017-03-30 Thread Julian Seward
https://bugs.kde.org/show_bug.cgi?id=358697 Julian Seward <jsew...@acm.org> changed: What|Removed |Added Resolution|--- |FIXED

[valgrind] [Bug 377698] Missing memory check for futex() uaddr arg for FUTEX_WAKE and FUTEX_WAKE_BITSET, check only 4 args for FUTEX_WAKE_BITSET, and 2 args for FUTEX_TRYLOCK_PI

2017-03-22 Thread Julian Seward
https://bugs.kde.org/show_bug.cgi?id=377698 Julian Seward <jsew...@acm.org> changed: What|Removed |Added CC||jsew...@acm.org --- C

[valgrind] [Bug 377698] Missing memory check for futex() uaddr arg for FUTEX_WAKE and FUTEX_WAKE_BITSET, check only 4 args for FUTEX_WAKE_BITSET, and 2 args for FUTEX_TRYLOCK_PI

2017-03-22 Thread Julian Seward
https://bugs.kde.org/show_bug.cgi?id=377698 --- Comment #7 from Julian Seward <jsew...@acm.org> --- (In reply to Diane M from comment #6) > I believe the if is necessary, because it is checking whether the function > pointer is defined, [..] Oh, you're right. I missed that. r+ t

[valgrind] [Bug 375839] Temporary storage exhusted , when long sequence of vfmadd231ps instructions to be executed

2017-03-29 Thread Julian Seward
https://bugs.kde.org/show_bug.cgi?id=375839 Julian Seward <jsew...@acm.org> changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Reso

[valgrind] [Bug 375839] Temporary storage exhusted , when long sequence of vfmadd231ps instructions to be executed

2017-03-27 Thread Julian Seward
https://bugs.kde.org/show_bug.cgi?id=375839 --- Comment #4 from Julian Seward <jsew...@acm.org> --- I should add: as a workaround, you can try specifying --vex-guest-max-insns=25 and if that still doesn't work, lowering the value towards zero. You shouldn't go below about 10. Lower

[valgrind] [Bug 375839] Temporary storage exhusted , when long sequence of vfmadd231ps instructions to be executed

2017-03-27 Thread Julian Seward
https://bugs.kde.org/show_bug.cgi?id=375839 Julian Seward <jsew...@acm.org> changed: What|Removed |Added CC||rsbul...@gma

[valgrind] [Bug 378068] valgrind crashes on AVX2 function in FFmpeg

2017-03-27 Thread Julian Seward
https://bugs.kde.org/show_bug.cgi?id=378068 Julian Seward <jsew...@acm.org> changed: What|Removed |Added Resolution|--- |DUPLICATE

[valgrind] [Bug 377966] disInstr(arm64): unhandled instruction 0xD50B7425 (dc zva,)

2017-03-23 Thread Julian Seward
https://bugs.kde.org/show_bug.cgi?id=377966 --- Comment #1 from Julian Seward <jsew...@acm.org> --- (In reply to John Reiser from comment #0) > instruction; it [allocates and] clears the cache line whose address > corresponds to the contents of register x5. Yes, ppc has something

[valgrind] [Bug 303877] valgrind doesn't support compressed debuginfo sections.

2017-03-20 Thread Julian Seward
https://bugs.kde.org/show_bug.cgi?id=303877 Bug 303877 depends on bug 377717, which changed state. Bug 377717 Summary: Fix massive space leak when reading compressed debuginfo sections https://bugs.kde.org/show_bug.cgi?id=377717 What|Removed |Added

[valgrind] [Bug 377717] Fix massive space leak when reading compressed debuginfo sections

2017-03-20 Thread Julian Seward
https://bugs.kde.org/show_bug.cgi?id=377717 Julian Seward <jsew...@acm.org> changed: What|Removed |Added Resolution|--- |FIXED

[valgrind] [Bug 377717] New: Fix massive space leak when reading compressed debuginfo sections

2017-03-17 Thread Julian Seward
https://bugs.kde.org/show_bug.cgi?id=377717 Bug ID: 377717 Summary: Fix massive space leak when reading compressed debuginfo sections Product: valgrind Version: 3.13 SVN Platform: Other OS: Linux

[valgrind] [Bug 303877] valgrind doesn't support compressed debuginfo sections.

2017-03-17 Thread Julian Seward
https://bugs.kde.org/show_bug.cgi?id=303877 Julian Seward <jsew...@acm.org> changed: What|Removed |Added Depends on||377717 Reference

[valgrind] [Bug 377717] Fix massive space leak when reading compressed debuginfo sections

2017-03-17 Thread Julian Seward
https://bugs.kde.org/show_bug.cgi?id=377717 --- Comment #1 from Julian Seward <jsew...@acm.org> --- Created attachment 104607 --> https://bugs.kde.org/attachment.cgi?id=104607=edit Fix A fix. Largely rewrites get_slowcase, documents abovementioned invariant, and adds a bunch

[valgrind] [Bug 375839] Temporary storage exhausted , when long sequence of vfmadd231ps instructions to be executed

2017-04-10 Thread Julian Seward
https://bugs.kde.org/show_bug.cgi?id=375839 --- Comment #13 from Julian Seward <jsew...@acm.org> --- (In reply to ux from comment #12) > Thread 1: status = VgTs_Runnable (lwpid 5547) > ==5547==at 0x5BF9BE: ff_vp9_idct_iadst_16x16_add_avx2 (vp9itxfm.asm:2149) > ==5547==

[valgrind] [Bug 375839] Temporary storage exhausted , when long sequence of vfmadd231ps instructions to be executed

2017-04-11 Thread Julian Seward
https://bugs.kde.org/show_bug.cgi?id=375839 --- Comment #20 from Julian Seward <jsew...@acm.org> --- (In reply to ux from comment #19) > Seems to work, all our VP9 tests pass with this. Thanks! Committed as vex r3346. -- You are receiving this mail because: You are watching all bug changes.

[valgrind] [Bug 375839] Temporary storage exhausted , when long sequence of vfmadd231ps instructions to be executed

2017-04-10 Thread Julian Seward
https://bugs.kde.org/show_bug.cgi?id=375839 Julian Seward <jsew...@acm.org> changed: What|Removed |Added Summary|Temporary storage exhusted |Temporary storage exh

[valgrind] [Bug 375839] Temporary storage exhusted , when long sequence of vfmadd231ps instructions to be executed

2017-04-10 Thread Julian Seward
https://bugs.kde.org/show_bug.cgi?id=375839 --- Comment #11 from Julian Seward <jsew...@acm.org> --- Uh, I thought I fixed it pretty comprehensively in r3344. Anyway, can you get me please a copy of the basic block that contains the failing address? at 0x

[valgrind] [Bug 375839] Temporary storage exhausted , when long sequence of vfmadd231ps instructions to be executed

2017-04-10 Thread Julian Seward
https://bugs.kde.org/show_bug.cgi?id=375839 --- Comment #16 from Julian Seward <jsew...@acm.org> --- (In reply to ux from comment #15) > My bad. So this block? > Full function in attachment. Ok .. nearly there. Could you please disassemble the function using the normal AT syntax

[valgrind] [Bug 375839] Temporary storage exhausted , when long sequence of vfmadd231ps instructions to be executed

2017-04-11 Thread Julian Seward
https://bugs.kde.org/show_bug.cgi?id=375839 --- Comment #18 from Julian Seward <jsew...@acm.org> --- Try this. Does it help? Index: priv/guest_amd64_toIR.c === --- priv/guest_amd64_toIR.c (revision 3345) ++

[valgrind] [Bug 378732] False positive "bad free" on recent versions of bash

2017-04-13 Thread Julian Seward
https://bugs.kde.org/show_bug.cgi?id=378732 --- Comment #1 from Julian Seward <jsew...@acm.org> --- Reuben! Per Chet's last comment line There's no place where that value is part of a data segment. I think that's a misreading of V's (admittedly ambiguous) claim about the segment. I

[valgrind] [Bug 378732] False positive "bad free" on recent versions of bash

2017-04-13 Thread Julian Seward
https://bugs.kde.org/show_bug.cgi?id=378732 --- Comment #5 from Julian Seward <jsew...@acm.org> --- (In reply to rrt from comment #2) > By default, bash seems to use its own malloc (and certainly in the case > where I do a default "./configure && make" from git sour

[valgrind] [Bug 344524] store conditional of guest applications always fail - observed on Octeon3(MIPS)

2017-04-20 Thread Julian Seward
https://bugs.kde.org/show_bug.cgi?id=344524 --- Comment #17 from Julian Seward <jsew...@acm.org> --- Also, your implementation uses guest_state.LLaddr == 0 to mean "there is no transaction in progress". So guest_state.LLaddr == 0 has a special meaning that is different from

[valgrind] [Bug 344524] store conditional of guest applications always fail - observed on Octeon3(MIPS)

2017-04-20 Thread Julian Seward
https://bugs.kde.org/show_bug.cgi?id=344524 --- Comment #18 from Julian Seward <jsew...@acm.org> --- Actually, I'd prefer to have it so that any attempt to do StoreCond will cause all following attempts to fail, up until a new LoadLinked is done. How does that sound? LoadLinke

[valgrind] [Bug 344524] store conditional of guest applications always fail - observed on Octeon3(MIPS)

2017-04-20 Thread Julian Seward
https://bugs.kde.org/show_bug.cgi?id=344524 --- Comment #16 from Julian Seward <jsew...@acm.org> --- (In reply to Maran Pakkirisamy from comment #8) Maran, I was studying this bug and your fix, so as to see how to apply it to ARM. I have a question: > With the update, only step 3 i

[valgrind] [Bug 344524] store conditional of guest applications always fail - observed on Octeon3(MIPS)

2017-04-20 Thread Julian Seward
https://bugs.kde.org/show_bug.cgi?id=344524 --- Comment #19 from Julian Seward <jsew...@acm.org> --- Hmm, even that is too relaxed, because it doesn't reject mismatched load vs store sizes. Here's a variant that does check sizes, and uses size == 0 to mean "no transaction pending&qu

[krita] [Bug 377407] New: segfault in libkritaflake.so.16.0.0

2017-03-08 Thread Julian Nymark
https://bugs.kde.org/show_bug.cgi?id=377407 Bug ID: 377407 Summary: segfault in libkritaflake.so.16.0.0 Product: krita Version: 3.1.2 Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity:

[valgrind] [Bug 370028] Reduce the number of compiler warnings on MIPS platforms

2017-03-06 Thread Julian Seward
https://bugs.kde.org/show_bug.cgi?id=370028 Julian Seward <jsew...@acm.org> changed: What|Removed |Added CC||jsew...@acm.org --- C

[valgrind] [Bug 373166] drd and helgrind will crash wth vex amd64->IR: unhandled instruction bytes 0xFF 0xFF 0x48 0x85 0xC0 0x74 0x8 0x4D 0x89 0xE7

2017-03-06 Thread Julian Seward
https://bugs.kde.org/show_bug.cgi?id=373166 Julian Seward <jsew...@acm.org> changed: What|Removed |Added CC||jsew...@acm.org --- C

[valgrind] [Bug 344139] vex x86->IR: unhandled instruction bytes: 0x36 0x8A 0x18 0x22 (and many other examples)

2017-03-06 Thread Julian Seward
https://bugs.kde.org/show_bug.cgi?id=344139 Julian Seward <jsew...@acm.org> changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Reso

[valgrind] [Bug 372185] Support of valgrind on ARMv8 with 32 bit executable

2017-03-06 Thread Julian Seward
https://bugs.kde.org/show_bug.cgi?id=372185 --- Comment #2 from Julian Seward <jsew...@acm.org> --- The current trunk supports ARMv8 32 bit instructions, almost everything except conversions to/from 16-bit floats. Give it a try. -- You are receiving this mail because: You are watching a

[valgrind] [Bug 372185] Support of valgrind on ARMv8 with 32 bit executable

2017-03-06 Thread Julian Seward
https://bugs.kde.org/show_bug.cgi?id=372185 Julian Seward <jsew...@acm.org> changed: What|Removed |Added Resolution|--- |FIXED

[valgrind] [Bug 371503] disInstr(arm64): unhandled instruction 0xF89F0000

2017-03-06 Thread Julian Seward
https://bugs.kde.org/show_bug.cgi?id=371503 --- Comment #1 from Julian Seward <jsew...@acm.org> --- Does this still happen with the trunk? It has supported "PRFM (register)" since 2015-08-16. -- You are receiving this mail because: You are watching all bug changes.

  1   2   3   4   5   6   7   8   9   10   >