[valgrind] [Bug 382515] valgrind: "Assertion 'di->have_dinfo' failed." on wine's dlls/mscoree/tests/mscoree.c

2017-07-31 Thread Austin English
https://bugs.kde.org/show_bug.cgi?id=382515 --- Comment #12 from Austin English <austinengl...@gmail.com> --- (In reply to Philippe Waroquiers from comment #11) > Note that the patch is compiling on linux, but is completely untested. > So, expect fire, smoke and explosions ... Tha

[valgrind] [Bug 382515] valgrind: "Assertion 'di->have_dinfo' failed." on wine's dlls/mscoree/tests/mscoree.c

2017-07-28 Thread Austin English
https://bugs.kde.org/show_bug.cgi?id=382515 --- Comment #8 from Austin English <austinengl...@gmail.com> --- (In reply to Philippe Waroquiers from comment #6) > The valgrind code expects something very precise as a header. > See function static void* find_pdb_header( vo

[valgrind] [Bug 382515] valgrind: "Assertion 'di->have_dinfo' failed." on wine's dlls/mscoree/tests/mscoree.c

2017-07-28 Thread Austin English
https://bugs.kde.org/show_bug.cgi?id=382515 --- Comment #7 from Austin English <austinengl...@gmail.com> --- Created attachment 106926 --> https://bugs.kde.org/attachment.cgi?id=106926=edit debug log 2 with --trace-symtab=yes --trace-symtab-patt=*mscorlib* -- You are receiving

[valgrind] [Bug 382515] valgrind: "Assertion 'di->have_dinfo' failed." on wine's dlls/mscoree/tests/mscoree.c

2017-07-24 Thread Austin English
https://bugs.kde.org/show_bug.cgi?id=382515 --- Comment #5 from Austin English <austinengl...@gmail.com> --- Forgot to say, first line of mingw64's pdb is: BSJB PDB V1.0 first character is \042 -- You are receiving this mail because: You are watching all bug changes.

[valgrind] [Bug 382515] valgrind: "Assertion 'di->have_dinfo' failed." on wine's dlls/mscoree/tests/mscoree.c

2017-07-24 Thread Austin English
https://bugs.kde.org/show_bug.cgi?id=382515 --- Comment #4 from Austin English <austinengl...@gmail.com> --- (In reply to Philippe Waroquiers from comment #3) > This find_pdb_header is searching for a specific character '\032' > and the string "Microsoft C/C++" > I

[valgrind] [Bug 382515] valgrind: "Assertion 'di->have_dinfo' failed." on wine's dlls/mscoree/tests/mscoree.c

2017-07-21 Thread Austin English
https://bugs.kde.org/show_bug.cgi?id=382515 --- Comment #2 from Austin English <austinengl...@gmail.com> --- Created attachment 106785 --> https://bugs.kde.org/attachment.cgi?id=106785=edit debug log -- You are receiving this mail because: You are watching all bug changes.

[valgrind] [Bug 382515] New: valgrind: "Assertion 'di->have_dinfo' failed." on wine's dlls/mscoree/tests/mscoree.c

2017-07-19 Thread Austin English
piled Sources OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: jsew...@acm.org Reporter: austinengl...@gmail.com Target Milestone: --- =8481== Warning: Missing or un-stat-able /home

[valgrind] [Bug 380869] valgrind has issues with mesa comiled with CFLAGS="-march=corei7"

2017-06-06 Thread Austin English
https://bugs.kde.org/show_bug.cgi?id=380869 --- Comment #11 from Austin English <austinengl...@gmail.com> --- @Henri, I've attached logs use radeonsi_dri.so instead of swrast (which is what I was using before investigating the issue). This contains the repe instruction as before. I'v

[valgrind] [Bug 380869] valgrind has issues with mesa comiled with CFLAGS="-march=corei7"

2017-06-06 Thread Austin English
https://bugs.kde.org/show_bug.cgi?id=380869 --- Comment #10 from Austin English <austinengl...@gmail.com> --- Created attachment 105950 --> https://bugs.kde.org/attachment.cgi?id=105950=edit radeonsi_dri_64.so -- You are receiving this mail because: You are watching all bug changes.

[valgrind] [Bug 380869] valgrind has issues with mesa comiled with CFLAGS="-march=corei7"

2017-06-06 Thread Austin English
https://bugs.kde.org/show_bug.cgi?id=380869 --- Comment #9 from Austin English <austinengl...@gmail.com> --- Created attachment 105949 --> https://bugs.kde.org/attachment.cgi?id=105949=edit radeonsi_dri_32.so Had to use xz, bzip2 was over the limit. -- You are receiving this mai

[valgrind] [Bug 380869] valgrind has issues with mesa comiled with CFLAGS="-march=corei7"

2017-06-06 Thread Austin English
https://bugs.kde.org/show_bug.cgi?id=380869 --- Comment #8 from Austin English <austinengl...@gmail.com> --- Created attachment 105948 --> https://bugs.kde.org/attachment.cgi?id=105948=edit log with march disabled, using radeonsi -- You are receiving this mail because: You are wat

[valgrind] [Bug 380869] valgrind has issues with mesa comiled with CFLAGS="-march=corei7"

2017-06-06 Thread Austin English
https://bugs.kde.org/show_bug.cgi?id=380869 --- Comment #7 from Austin English <austinengl...@gmail.com> --- Created attachment 105947 --> https://bugs.kde.org/attachment.cgi?id=105947=edit log with march enabled, using radeonsi -- You are receiving this mail because: You are watchin

[valgrind] [Bug 380869] valgrind has issues with mesa comiled with CFLAGS="-march=corei7"

2017-06-05 Thread Austin English
https://bugs.kde.org/show_bug.cgi?id=380869 --- Comment #6 from Austin English <austinengl...@gmail.com> --- So, while testing again, I realized I hadn't rerun the test with software rendering (the full valgrind run and individual test runs are two different scripts, and the later wasn't f

[valgrind] [Bug 380869] valgrind has issues with mesa comiled with CFLAGS="-march=corei7"

2017-06-05 Thread Austin English
https://bugs.kde.org/show_bug.cgi?id=380869 --- Comment #5 from Austin English <austinengl...@gmail.com> --- Created attachment 105937 --> https://bugs.kde.org/attachment.cgi?id=105937=edit swrast_dir64.so -- You are receiving this mail because: You are watching all bug changes.

[valgrind] [Bug 380869] valgrind has issues with mesa comiled with CFLAGS="-march=corei7"

2017-06-05 Thread Austin English
https://bugs.kde.org/show_bug.cgi?id=380869 --- Comment #4 from Austin English <austinengl...@gmail.com> --- Created attachment 105936 --> https://bugs.kde.org/attachment.cgi?id=105936=edit swrast_dir32.so -- You are receiving this mail because: You are watching all bug changes.

[valgrind] [Bug 380869] valgrind has issues with mesa comiled with CFLAGS="-march=corei7"

2017-06-05 Thread Austin English
https://bugs.kde.org/show_bug.cgi?id=380869 --- Comment #3 from Austin English <austinengl...@gmail.com> --- Created attachment 105935 --> https://bugs.kde.org/attachment.cgi?id=105935=edit this time, without -march=corei7 -- You are receiving this mail because: You are watchin

[valgrind] [Bug 380869] valgrind has issues with mesa comiled with CFLAGS="-march=corei7"

2017-06-05 Thread Austin English
https://bugs.kde.org/show_bug.cgi?id=380869 --- Comment #2 from Austin English <austinengl...@gmail.com> --- Created attachment 105934 --> https://bugs.kde.org/attachment.cgi?id=105934=edit full bad output -- You are receiving this mail because: You are watching all bug changes.

[valgrind] [Bug 380869] New: valgrind has issues with mesa comiled with CFLAGS="-march=corei7"

2017-06-05 Thread Austin English
9 0x05935782 X11DRV_WineGL_InitOpenglInfo+0x2fe() [/home/austin/wine-valgrind/dlls/winex11.drv/opengl.c:502] in winex11 (0x04b8f2d8) 10 0x05936f92 init_opengl+0xfbe(once=0x5993e00, param=0x0(nil), context=(nil)) [/home/austin/wine-valgrind/dlls/winex11.drv/opengl.c:679] in winex11 (0x04b8f4e8) This

[valgrind] [Bug 365327] Support macOS Sierra (10.12)

2017-04-25 Thread Austin English
https://bugs.kde.org/show_bug.cgi?id=365327 --- Comment #15 from Austin English <austinengl...@gmail.com> --- (In reply to Louis Brunner from comment #12) > Created attachment 104964 [details] > macOS Sierra incomplete support > > I have been working on a patch to su

[valgrind] [Bug 365327] Support macOS Sierra (10.12)

2017-03-15 Thread Austin English
https://bugs.kde.org/show_bug.cgi?id=365327 Austin English <austinengl...@gmail.com> changed: What|Removed |Added CC||aust

[valgrind] [Bug 339017] (meta) Valgrind 3.10 cannot load wine on OS X

2017-02-12 Thread Austin English
https://bugs.kde.org/show_bug.cgi?id=339017 --- Comment #10 from Austin English <austinengl...@gmail.com> --- (In reply to Rhys Kidd from comment #8) > We have another user, Austin, who is testing some Wine-specific patches and > will aim to run Wine's unit tests under Valg

[valgrind] [Bug 349804] wine/osx: mmap-FIXED(0x1000, 1073741824) failed in UME (load_segment2)

2017-02-12 Thread Austin English
https://bugs.kde.org/show_bug.cgi?id=349804 --- Comment #10 from Austin English <austinengl...@gmail.com> --- (In reply to Austin English from comment #9) > (In reply to Austin English from comment #8) > > Created attachment 94210 [details] > > wine+valgrind output > >

[valgrind] [Bug 349804] wine/osx: mmap-FIXED(0x1000, 1073741824) failed in UME (load_segment2)

2017-02-12 Thread Austin English
https://bugs.kde.org/show_bug.cgi?id=349804 --- Comment #9 from Austin English <austinengl...@gmail.com> --- (In reply to Austin English from comment #8) > Created attachment 94210 [details] > wine+valgrind output > > Using wine-1.7.50-26-g6038e2a and valgrind-3.11.0-SVN-r155

[valgrind] [Bug 211031] valgrind doesn't show symbols for programs compiled with mingw's gcc

2017-02-11 Thread Austin English
https://bugs.kde.org/show_bug.cgi?id=211031 --- Comment #14 from Austin English <austinengl...@gmail.com> --- (In reply to Austin English from comment #13) > This is also relevant again for wine-gecko. Upstream Firefox moved to > require Visual Studio 2013+, and those newer format PDB

[valgrind] [Bug 295084] Hard-coded /usr/include

2017-02-07 Thread Austin English
https://bugs.kde.org/show_bug.cgi?id=295084 --- Comment #10 from Austin English <austinengl...@gmail.com> --- (In reply to Rhys Kidd from comment #9) > I'm almost certain there's a problem with your local copy of Xcode or with > multiple versions of Xcode tripping up. > > It

[valgrind] [Bug 376027] New: wine's comdlg32/filedlg.c test hangs under valgrind

2017-02-05 Thread Austin English
https://bugs.kde.org/show_bug.cgi?id=376027 Bug ID: 376027 Summary: wine's comdlg32/filedlg.c test hangs under valgrind Product: valgrind Version: 3.13 SVN Platform: Compiled Sources URL:

[valgrind] [Bug 350228] Unhandled ioctl 0x6458 (i965/mesa)

2017-01-25 Thread Austin English
https://bugs.kde.org/show_bug.cgi?id=350228 Austin English <austinengl...@gmail.com> changed: What|Removed |Added Status|UNCONFIRMED |RE

[krita] [Bug 375027] Krita Gemini doesn't support the n-trig pen of a surface pro, even if wintab is installed.

2017-01-24 Thread Austin
https://bugs.kde.org/show_bug.cgi?id=375027 --- Comment #3 from Austin <thecourie...@gmail.com> --- So I'm SOL for the moment. That's ok! I don't mind giving you guys the $10 for now, I just hope eventually there will be the opportunity for me to get an update or Krita Sketch (if tha

[valgrind] [Bug 354809] Error message for unsupported platform is unhelpful

2017-01-21 Thread Austin English
https://bugs.kde.org/show_bug.cgi?id=354809 --- Comment #1 from Austin English <austinengl...@gmail.com> --- With: austin@debian-laptop:~/src/valgrind$ ./vg-in-place --version -v valgrind-3.13.0.SVN-16209-vex-3299 the error message has improved (64-bit valgrind, 32-bit binary): austin@

[krita] [Bug 375028] Stylus is unaligned

2017-01-13 Thread Austin
https://bugs.kde.org/show_bug.cgi?id=375028 --- Comment #1 from Austin <thecourie...@gmail.com> --- I forgot to mention I am on a surface pro 4 with surface pen using Krita Gemini through Steam. -- You are receiving this mail because: You are watching all bug changes.

[krita] [Bug 375028] New: Stylus is unaligned

2017-01-13 Thread Austin
https://bugs.kde.org/show_bug.cgi?id=375028 Bug ID: 375028 Summary: Stylus is unaligned Product: krita Version: unspecified Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: normal

[krita] [Bug 375027] New: Stylus isn't calibrated

2017-01-13 Thread Austin
https://bugs.kde.org/show_bug.cgi?id=375027 Bug ID: 375027 Summary: Stylus isn't calibrated Product: krita Version: unspecified Platform: MS Windows OS: MS Windows Status: UNCONFIRMED Severity: major

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

2016-12-04 Thread Austin English
https://bugs.kde.org/show_bug.cgi?id=344139 --- Comment #2 from Austin English <austinengl...@gmail.com> --- To give a bit more info (and for myself in the future ;). This is still present in development wine (wine-1.9.24-105-g1d3b944) and valgrind (valgrind-3.13.0.SVN, #define VGSVN

[valgrind] [Bug 352395] Please provide SVN revision info in --version

2016-11-28 Thread Austin English
https://bugs.kde.org/show_bug.cgi?id=352395 --- Comment #29 from Austin English <austinengl...@gmail.com> --- (In reply to Philippe Waroquiers from comment #28) > Strange that the git-svn version does not show a M(odified) marker. Yeah, I noticed that too. I'll try to remember to f

[valgrind] [Bug 295084] Hard-coded /usr/include

2016-11-28 Thread Austin English
https://bugs.kde.org/show_bug.cgi?id=295084 --- Comment #8 from Austin English <austinengl...@gmail.com> --- To be more explicit: Austins-Mac-mini:~ austin$ xcode-select --install xcode-select: note: install requested for command line developer tools Austins-Mac-mini:~ austin$ ls /usr/

[valgrind] [Bug 295084] Hard-coded /usr/include

2016-11-28 Thread Austin English
https://bugs.kde.org/show_bug.cgi?id=295084 --- Comment #7 from Austin English <austinengl...@gmail.com> --- (In reply to Rhys Kidd from comment #6) > Austin, > > Before you do, can you please confirm that you have the latest Xcode Command > Line Tools installed? It is

[valgrind] [Bug 295084] Hard-coded /usr/include

2016-11-28 Thread Austin English
https://bugs.kde.org/show_bug.cgi?id=295084 Austin English <austinengl...@gmail.com> changed: What|Removed |Added CC||aust

[valgrind] [Bug 354809] Error message for unsupported platform is unhelpful

2016-11-28 Thread Austin English
https://bugs.kde.org/show_bug.cgi?id=354809 Austin English <austinengl...@gmail.com> changed: What|Removed |Added CC||aust

[valgrind] [Bug 352395] Please provide SVN revision info in --version

2016-11-28 Thread Austin English
https://bugs.kde.org/show_bug.cgi?id=352395 --- Comment #27 from Austin English <austinengl...@gmail.com> --- (In reply to Austin English from comment #26) > Created attachment 102512 [details] > try 10, extra sanity checks > > try 9 works for me, but I put some extra sanity ch

[valgrind] [Bug 352395] Please provide SVN revision info in --version

2016-11-28 Thread Austin English
https://bugs.kde.org/show_bug.cgi?id=352395 --- Comment #26 from Austin English <austinengl...@gmail.com> --- Created attachment 102512 --> https://bugs.kde.org/attachment.cgi?id=102512=edit try 10, extra sanity checks try 9 works for me, but I put some extra sanity checks in.

[valgrind] [Bug 352395] Please provide SVN revision info in --version

2016-11-27 Thread Austin English
https://bugs.kde.org/show_bug.cgi?id=352395 --- Comment #22 from Austin English <austinengl...@gmail.com> --- (In reply to Ivo Raisr from comment #20) > Patch #6 seems to be working well. I tested it on Solaris, inside SVN tree, > outside and after 'make dist'. > > In ad

[valgrind] [Bug 352395] Please provide SVN revision info in --version

2016-11-27 Thread Austin English
https://bugs.kde.org/show_bug.cgi?id=352395 --- Comment #17 from Austin English <austinengl...@gmail.com> --- (In reply to Philippe Waroquiers from comment #16) > Created attachment 102468 [details] > try 6 : modified to have vgversion.h also handled as part of make dist > >

[valgrind] [Bug 352395] Please provide SVN revision info in --version

2016-11-21 Thread Austin English
https://bugs.kde.org/show_bug.cgi?id=352395 --- Comment #13 from Austin English <austinengl...@gmail.com> --- (In reply to Austin English from comment #12) > How commonly are tarballs created/used for random SVN revisions rather than > releases? > > To be frank, I'm no

[valgrind] [Bug 352395] Please provide SVN revision info in --version

2016-11-21 Thread Austin English
https://bugs.kde.org/show_bug.cgi?id=352395 --- Comment #12 from Austin English <austinengl...@gmail.com> --- How commonly are tarballs created/used for random SVN revisions rather than releases? To be frank, I'm not very experienced with makefiles, and the current changes have alread

[dolphin] [Bug 360809] Dolphin crashes when copy a file and paste it in the same folder(no problem when pasting same-name file from another folder)

2016-03-21 Thread Austin via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=360809 Austin <personguy...@gmail.com> changed: What|Removed |Added CC||personguy...@gma

<    1   2