[valgrind] [Bug 385279] [PATCH] unhandled syscall: mach:43 (mach_generate_activity_id)

2017-12-21 Thread FX
https://bugs.kde.org/show_bug.cgi?id=385279

--- Comment #5 from FX  ---
Louis' patch fixes it for me. I've been able to run various binaries (bash,
zsh, clang, etc.) under valgrind on macOS 10.13.2 without any error.

Many binaries, however, generate some messages like early in their execution:

--55772-- UNKNOWN mach_msg unhandled MACH_SEND_TRAILER option
--55772-- UNKNOWN mach_msg unhandled MACH_SEND_TRAILER option (repeated 2
times)
--55772-- UNKNOWN mach_msg unhandled MACH_SEND_TRAILER option (repeated 4
times)
--55772-- UNKNOWN mach_msg unhandled MACH_SEND_TRAILER option (repeated 8
times)

-- 
You are receiving this mail because:
You are watching all bug changes.

[valgrind] [Bug 385279] [PATCH] unhandled syscall: mach:43 (mach_generate_activity_id)

2017-12-21 Thread FX
https://bugs.kde.org/show_bug.cgi?id=385279

--- Comment #7 from FX  ---
No, wrote to fast :)
I found another issue:

$ /tmp/bin/valgrind /usr/bin/lpq
==55783== Memcheck, a memory error detector
==55783== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al.
==55783== Using Valgrind-3.14.0.GIT and LibVEX; rerun with -h for copyright
info
==55783== Command: /usr/bin/lpq
==55783== 
--55783-- UNKNOWN mach_msg unhandled MACH_SEND_TRAILER option
--55783-- UNKNOWN mach_msg unhandled MACH_SEND_TRAILER option (repeated 2
times)
--55783-- UNKNOWN mach_msg unhandled MACH_SEND_TRAILER option (repeated 4
times)
--55783-- UNKNOWN mach_msg unhandled MACH_SEND_TRAILER option (repeated 8
times)
==55783== valgrind: Unrecognised instruction at address 0x1010bfd93.
==55783==at 0x1010BFD93: _dispatch_kq_init (in
/usr/lib/system/libdispatch.dylib)
==55783==by 0x1010BDD4F: _dispatch_client_callout (in
/usr/lib/system/libdispatch.dylib)
==55783==by 0x1010BDD02: dispatch_once_f (in
/usr/lib/system/libdispatch.dylib)
==55783==by 0x1010DBAAE: _dispatch_kq_poll (in
/usr/lib/system/libdispatch.dylib)
==55783==by 0x1010DB735: _dispatch_kq_drain (in
/usr/lib/system/libdispatch.dylib)
==55783==by 0x1010DAB03: _dispatch_kq_unote_update (in
/usr/lib/system/libdispatch.dylib)
==55783==by 0x1010D5E33: _dispatch_source_refs_register (in
/usr/lib/system/libdispatch.dylib)
==55783==by 0x1010D5F5D: _dispatch_source_finalize_activation (in
/usr/lib/system/libdispatch.dylib)
==55783==by 0x1010CEF49: _dispatch_queue_resume_finalize_activation (in
/usr/lib/system/libdispatch.dylib)
==55783==by 0x1014734F6: _notify_lib_init (in
/usr/lib/system/libsystem_notify.dylib)
==55783==by 0x101473B89: notify_register_dispatch (in
/usr/lib/system/libsystem_notify.dylib)
==55783==by 0x100332C27: CFUserNotificationCreate (in
/System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation)
==55783== Your program just tried to execute an instruction that Valgrind
==55783== did not recognise.  There are two possible reasons for this.

Several other native Apple programs (Preview, TextEdit) as well as non-Apple
(Atom) give the same crash and error stack (with different addresses).

-- 
You are receiving this mail because:
You are watching all bug changes.

[valgrind] [Bug 385279] [PATCH] unhandled syscall: mach:43 (mach_generate_activity_id)

2017-12-21 Thread FX
https://bugs.kde.org/show_bug.cgi?id=385279

--- Comment #9 from FX  ---
The lpq issue: with the patch from this PR, I trigger 383723. Adding the patch
at 383723, I get 380269. Adding the tentative patch posted at 380269, I still
get an error:

==63832== Thread 2:
==63832== Invalid read of size 4
==63832==at 0x1014E1E9B: _pthread_wqthread (in
/usr/lib/system/libsystem_pthread.dylib)
==63832==by 0x1014E1C4C: start_wqthread (in
/usr/lib/system/libsystem_pthread.dylib)
==63832==  Address 0x18 is not stack'd, malloc'd or (recently) free'd
==63832== 
==63832== 
==63832== Process terminating with default action of signal 11 (SIGSEGV)
==63832==  Access not within mapped region at address 0x18
==63832==at 0x1014E1E9B: _pthread_wqthread (in
/usr/lib/system/libsystem_pthread.dylib)
==63832==by 0x1014E1C4C: start_wqthread (in
/usr/lib/system/libsystem_pthread.dylib)
==63832==  If you believe this happened as a result of a stack
==63832==  overflow in your program's main thread (unlikely but
==63832==  possible), you can try to increase the size of the
==63832==  main thread stack using the --main-stacksize= flag.
==63832==  The main thread stack size used in this run was 8388608.
--63832:0:schedule VG_(sema_down): read returned -4

valgrind: m_scheduler/scheduler.c:952 (void run_thread_for_a_while(HWord *, Int
*, ThreadId, HWord, Bool)): Assertion 'VG_(in_generated_code) == False' failed.

host stacktrace:
==63832==at 0x258053C2B: ???
==63832==by 0x258053FBC: ???
==63832==by 0x258053F93: ???
==63832==by 0x2580EADFB: ???
==63832==by 0x2580E9788: ???
==63832==by 0x2580FB7DE: ???
==63832==by 0x2580FBAAA: ???

sched status:
  running_tid=3

Thread 1: status = VgTs_WaitSys (lwpid 771)
==63832==at 0x1014AC562: __workq_kernreturn (in
/usr/lib/system/libsystem_kernel.dylib)
==63832==by 0x1014E1C27: _pthread_workqueue_addthreads (in
/usr/lib/system/libsystem_pthread.dylib)
==63832==by 0x1010D1E4D: _dispatch_global_queue_poke_slow (in
/usr/lib/system/libdispatch.dylib)
==63832==by 0x1010D91BD: _dispatch_mach_send_push (in
/usr/lib/system/libdispatch.dylib)
==63832==by 0x1010DD8C8: _voucher_activity_debug_channel_init (in
/usr/lib/system/libdispatch.dylib)
==63832==by 0x1010DBAFC: _dispatch_kq_poll (in
/usr/lib/system/libdispatch.dylib)
==63832==by 0x1010DB735: _dispatch_kq_drain (in
/usr/lib/system/libdispatch.dylib)
==63832==by 0x1010DAB03: _dispatch_kq_unote_update (in
/usr/lib/system/libdispatch.dylib)
==63832==by 0x1010D5E33: _dispatch_source_refs_register (in
/usr/lib/system/libdispatch.dylib)
==63832==by 0x1010D5F5D: _dispatch_source_finalize_activation (in
/usr/lib/system/libdispatch.dylib)
==63832==by 0x1010CEF49: _dispatch_queue_resume_finalize_activation (in
/usr/lib/system/libdispatch.dylib)
==63832==by 0x1014734F6: _notify_lib_init (in
/usr/lib/system/libsystem_notify.dylib)
==63832==by 0x101473B89: notify_register_dispatch (in
/usr/lib/system/libsystem_notify.dylib)
==63832==by 0x100332C27: CFUserNotificationCreate (in
/System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation)
==63832==by 0x1010BDD4F: _dispatch_client_callout (in
/usr/lib/system/libdispatch.dylib)
==63832==by 0x1010BDD02: dispatch_once_f (in
/usr/lib/system/libdispatch.dylib)
==63832==by 0x100332ADD: CFUserNotificationGetTypeID (in
/System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation)
==63832==by 0x1001ED210: -[CFPrefsPlistSource createSynchronizeMessage] (in
/System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation)
==63832==by 0x100375F96: -[NSOrderedSet objectsWithOptions:passingTest:]
(in
/System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation)
==63832==by 0x10037723E: +[NSOrderedSet orderedSetWithObject:] (in
/System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation)
==63832==by 0x100375CD2: -[NSOrderedSet objectWithOptions:passingTest:] (in
/System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation)
==63832==by 0x100375B64: -[NSOrderedSet isSubsetOfSet:] (in
/System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation)
==63832==by 0x10039BCE2: __CFGenerateReport (in
/System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation)
==63832==by 0x1001F5252: +[_CFXNotificationTokenRegistration
createTokenRegistration:token:connection:notifyToken:options:queue:handler:]
(in
/System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation)
==63832==by 0x1000E33E8: cupsLangGet (in /usr/lib/libcups.2.dylib)
==63832==by 0x1000E2A42: _cupsSetLocale (in /usr/lib/libcups.2.dylib)
==63832==by 0x10B72: ??? (in /usr/bin/lpq)
==63832==by 0x101131114: start (in /usr/lib/system/libdyld.dylib)

Thread 2: status = VgTs_Yielding (lwpid 4107)
==63832==at 0x1014E1E9B: _pthread_wqthread (in
/usr/lib/

[valgrind] [Bug 385279] [PATCH] unhandled syscall: mach:43 (mach_generate_activity_id)

2017-12-21 Thread FX
https://bugs.kde.org/show_bug.cgi?id=385279

--- Comment #11 from FX  ---
(In reply to Rhys Kidd from comment #10)
> Helpfully, there's a bug report tracking that too and a draft patch for that
> at https://bugs.kde.org/show_bug.cgi?id=380269

That's what I was saying. I'm seeing that error, after applying the draft patch
at 380269.

-- 
You are receiving this mail because:
You are watching all bug changes.

[valgrind] [Bug 383811] Support macOS High Sierra (10.13)

2017-09-10 Thread FX
https://bugs.kde.org/show_bug.cgi?id=383811

--- Comment #3 from FX  ---
With valgrind trunk and the patch in comment 1, after having run autogen.sh in
the source tree: configure && make work, and the resulting valgrind appears to
work. For example, it correctly determines on invalid write in a free'd block.
It also correctly detects unfree'd memory when it encounters it.

I have found, so far, two issues:

1. valgrind displays a warning about libsystem_kernel for any executable I run
(valid or invalid):

==90520== Syscall param msg->desc.port.name points to uninitialised byte(s)
==90520==at 0x100590E76: mach_msg_trap (in
/usr/lib/system/libsystem_kernel.dylib)
==90520==by 0x10059038F: mach_msg (in
/usr/lib/system/libsystem_kernel.dylib)
==90520==by 0x100589F3D: task_set_special_port (in
/usr/lib/system/libsystem_kernel.dylib)
==90520==by 0x1005F701A: _os_trace_create_debug_control_port (in
/usr/lib/system/libsystem_trace.dylib)
==90520==by 0x1005F72D0: _libtrace_init (in
/usr/lib/system/libsystem_trace.dylib)
==90520==by 0x1000BD9CC: libSystem_initializer (in
/usr/lib/libSystem.B.dylib)
==90520==by 0x1415F: dyld3::kdebug_trace_dyld_duration(unsigned int,
unsigned long long, unsigned long long, void ( block_pointer)()) (in
/usr/lib/dyld)
==90520==by 0x100019A09:
ImageLoaderMachO::doModInitFunctions(ImageLoader::LinkContext const&) (in
/usr/lib/dyld)
==90520==by 0x100019C39:
ImageLoaderMachO::doInitialization(ImageLoader::LinkContext const&) (in
/usr/lib/dyld)
==90520==by 0x10001516F:
ImageLoader::recursiveInitialization(ImageLoader::LinkContext const&, unsigned
int, char const*, ImageLoader::InitializerTimingList&,
ImageLoader::UninitedUpwards&) (in /usr/lib/dyld)
==90520==by 0x100015102:
ImageLoader::recursiveInitialization(ImageLoader::LinkContext const&, unsigned
int, char const*, ImageLoader::InitializerTimingList&,
ImageLoader::UninitedUpwards&) (in /usr/lib/dyld)
==90520==by 0x1000142A5:
ImageLoader::processInitializers(ImageLoader::LinkContext const&, unsigned int,
ImageLoader::InitializerTimingList&, ImageLoader::UninitedUpwards&) (in
/usr/lib/dyld)
==90520==  Address 0x10489f19c is on thread 1's stack
==90520==  in frame #2, created by task_set_special_port (???:)



2. When running "valgrind --leak-check=full", it issues a warning about dyld:

==90558== 72 bytes in 3 blocks are possibly lost in loss record 26 of 43
==90558==at 0x1000AB542: calloc (vg_replace_malloc.c:714)
==90558==by 0x1006C07E2: map_images_nolock (in /usr/lib/libobjc.A.dylib)
==90558==by 0x1006D37DA: objc_object::sidetable_retainCount() (in
/usr/lib/libobjc.A.dylib)
==90558==by 0x17C64: dyld::notifyBatchPartial(dyld_image_states, bool,
char const* (*)(dyld_image_states, unsigned int, dyld_image_info const*), bool,
bool) (in /usr/lib/dyld)
==90558==by 0x17E39: dyld::registerObjCNotifiers(void (*)(unsigned int,
char const* const*, mach_header const* const*), void (*)(char const*,
mach_header const*), void (*)(char const*, mach_header const*)) (in
/usr/lib/dyld)
==90558==by 0x10022284D: _dyld_objc_notify_register (in
/usr/lib/system/libdyld.dylib)
==90558==by 0x1006C0075: _objc_init (in /usr/lib/libobjc.A.dylib)
==90558==by 0x1001ACCE0: _os_object_init (in
/usr/lib/system/libdispatch.dylib)
==90558==by 0x1001ACCC7: libdispatch_init (in
/usr/lib/system/libdispatch.dylib)
==90558==by 0x1000BD9C2: libSystem_initializer (in
/usr/lib/libSystem.B.dylib)
==90558==by 0x1415F: dyld3::kdebug_trace_dyld_duration(unsigned int,
unsigned long long, unsigned long long, void ( block_pointer)()) (in
/usr/lib/dyld)
==90558==by 0x100019A09:
ImageLoaderMachO::doModInitFunctions(ImageLoader::LinkContext const&) (in
/usr/lib/dyld)




3. Trying to run /bin/bash under valgrind leads to this error:

--90616-- UNKNOWN mach_msg unhandled MACH_SEND_TRAILER option
--90616-- UNKNOWN mach_msg unhandled MACH_SEND_TRAILER option (repeated 2
times)
--90616-- UNKNOWN mach_msg unhandled MACH_SEND_TRAILER option (repeated 4
times)
--90616-- UNKNOWN mach_msg unhandled MACH_SEND_TRAILER option (repeated 8
times)
==90616== Syscall param mach_msg("rcv_name") contains uninitialised byte(s)
==90616==at 0x10076AE76: mach_msg_trap (in
/usr/lib/system/libsystem_kernel.dylib)
==90616==by 0x10076A38F: mach_msg (in
/usr/lib/system/libsystem_kernel.dylib)
==90616==by 0x1007D86F2: _os_trace_prefs_and_mode_refresh_slow (in
/usr/lib/system/libsystem_trace.dylib)
==90616==by 0x1007CEF06: _os_activity_create_addr (in
/usr/lib/system/libsystem_trace.dylib)
==90616==by 0x10055D219: ds_user_byuid (in
/usr/lib/system/libsystem_info.dylib)
==9061

[valgrind] [Bug 383811] New: Failure to build on macOS 10.13 High Sierra

2017-08-21 Thread FX
https://bugs.kde.org/show_bug.cgi?id=383811

Bug ID: 383811
   Summary: Failure to build on macOS 10.13 High Sierra
   Product: valgrind
   Version: 3.14 SVN
  Platform: Other
OS: OS X
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: jsew...@acm.org
  Reporter: fxcoud...@gcc.gnu.org
  Target Milestone: ---

- configure.ac needs to be adapted to allow for Apple LLVM version 9.* (line
157)
- configure.ac needs DARWIN_10_13 and other adjustments (lines 351 and below)

Then the build fails with:

Making all in coregrind
make[2]: *** No rule to make target `/usr/include/mach/mach_vm.defs', needed by
`m_mach/mach_vmUser.c'.  Stop.
make[1]: *** [all-recursive] Error 1
make: *** [all] Error 2

-- 
You are receiving this mail because:
You are watching all bug changes.

[dolphin] [Bug 503803] New: Dolphin freezes when selecting 3MF File

2025-05-05 Thread fx
https://bugs.kde.org/show_bug.cgi?id=503803

Bug ID: 503803
   Summary: Dolphin freezes when selecting 3MF File
Classification: Applications
   Product: dolphin
   Version: 25.04.0
  Platform: Manjaro
OS: Linux
Status: REPORTED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: dolphin-bugs-n...@kde.org
  Reporter: i...@gmx.de
CC: kfm-de...@kde.org
  Target Milestone: ---

Created attachment 180952
  --> https://bugs.kde.org/attachment.cgi?id=180952&action=edit
Error message from Dolphin in konsole

SUMMARY
Dolphin freezes when selecting any 3MF File.

STEPS TO REPRODUCE
1. Open Dolphin
2. Open folder with 3MF files inside
3. Select 3MF File => Dolphin freezes 

Error messages in Konsole and system info in attached screenshots


SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Manjaro KDE
KDE Plasma Version: 6.3.4
KDE Frameworks Version: 
Qt Version:

-- 
You are receiving this mail because:
You are watching all bug changes.

[dolphin] [Bug 503803] Dolphin freezes when selecting 3MF File

2025-05-05 Thread fx
https://bugs.kde.org/show_bug.cgi?id=503803

--- Comment #1 from fx  ---
Created attachment 180953
  --> https://bugs.kde.org/attachment.cgi?id=180953&action=edit
Dolphin Version

-- 
You are receiving this mail because:
You are watching all bug changes.

[dolphin] [Bug 503803] Dolphin freezes when selecting 3MF File

2025-05-05 Thread fx
https://bugs.kde.org/show_bug.cgi?id=503803

--- Comment #2 from fx  ---
Created attachment 180954
  --> https://bugs.kde.org/attachment.cgi?id=180954&action=edit
System Info

-- 
You are receiving this mail because:
You are watching all bug changes.

[dolphin] [Bug 503803] Dolphin freezes when selecting 3MF File

2025-05-05 Thread fx
https://bugs.kde.org/show_bug.cgi?id=503803

--- Comment #3 from fx  ---
Created attachment 180955
  --> https://bugs.kde.org/attachment.cgi?id=180955&action=edit
With this file dolphin freezes when i select it. maybe you can reproduce it
with this file

-- 
You are receiving this mail because:
You are watching all bug changes.

[dolphin] [Bug 503803] Dolphin freezes when selecting 3MF File

2025-05-09 Thread fx
https://bugs.kde.org/show_bug.cgi?id=503803

--- Comment #5 from fx  ---
(In reply to John Kizer from comment #4)
> Hi - merging this in with an existing bug report for what appears to be the
> same underlying issue. Thanks!
> 
> *** This bug has been marked as a duplicate of bug 503319 ***

Thank you and sorry for the duplicate

-- 
You are receiving this mail because:
You are watching all bug changes.

[kio-extras] [Bug 503319] Thumbnailer hangs on .3mf files

2025-05-16 Thread fx
https://bugs.kde.org/show_bug.cgi?id=503319

--- Comment #2 from fx  ---
I have disabled all thumbnails, but Dolphin is still getting unresponsive for
10s to 60s when selecting a 3MF File. 

When I disable "Informationen zum Element beim Überfahren anzeigen" in settings
"Ansicht", Dolphin runs wihout problems.

When I enable "Informationen zum Element beim Überfahren anzeigen" again,
Dolphin will get stuck again and i have this error in Konsole:

QProcess: Destroyed while process
("/usr/bin/baloo_filemetadata_temp_extractor") is still running.
org.kde.baloo.widgets: Extractor crashed when processing
QList("/home/fx/Schreibtisch/_3Druck/Rudi-Wohnmobil-Türstopper/Part Studio
1.3mf")

Sorry for german.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kio-extras] [Bug 503319] Thumbnailer hangs on .3mf files

2025-07-03 Thread fx
https://bugs.kde.org/show_bug.cgi?id=503319

--- Comment #4 from fx  ---
I've just tested it.
Same here, no more problems.

OS: Manjaro Linux x86_64
Kernel: Linux 6.15.3-1-MANJARO
Uptime: 7 mins
Packages: 1413 (pacman)[stable], 77 (flatpak-system), 6 (flatpak-user)
Shell: zsh 5.9
Display (DP-1): 5120x1440 @ 60 Hz in 49" [External]
DE: KDE Plasma 6.3.5
WM: KWin (Wayland)
WM Theme: Breeze
Theme: Breeze (BreathDark) [Qt], Breeze-Dark [GTK2], Breeze [GTK3]
Icons: breeze-dark [Qt], breeze-dark [GTK2/3/4]
Font: Noto Sans (10pt) [Qt], Noto Sans (10pt) [GTK2/3/4]
Cursor: breeze (42px)
Terminal: konsole 25.4.2
Terminal Font: Hack Nerd Font Mono (11pt)
CPU: AMD Ryzen 7 5800X3D (16) @ 3.40 GHz
GPU: AMD Radeon RX 7900 XTX [Discrete]
Memory: 3.42 GiB / 31.25 GiB (11%)
Swap: 0 B / 512.00 MiB (0%)
Disk (/): 378.89 GiB / 1.79 TiB (21%) - ext4
Local IP (enp6s0): 192.168.8.5/24
Locale: de_DE.UTF-8

-- 
You are receiving this mail because:
You are watching all bug changes.

[umbrello] [Bug 378399] New: Application crashes on Duplicate

2017-04-03 Thread Fx Lesaffre
https://bugs.kde.org/show_bug.cgi?id=378399

Bug ID: 378399
   Summary: Application crashes on Duplicate
   Product: umbrello
   Version: 2.21.2 (KDE Applications 16.12.2)
  Platform: Windows CE
OS: MS Windows
Status: UNCONFIRMED
  Severity: crash
  Priority: NOR
 Component: general
  Assignee: umbrello-de...@kde.org
  Reporter: fx.lesaf...@dmic.fr
  Target Milestone: ---

While you select the "Generalization arrow" tool and then right-click on an
item to duplicate it, Umbrello crashes and stops.

-- 
You are receiving this mail because:
You are watching all bug changes.

[umbrello] [Bug 378399] Application crashes on Duplicate

2017-04-05 Thread Fx Lesaffre
https://bugs.kde.org/show_bug.cgi?id=378399

--- Comment #3 from Fx Lesaffre  ---
1 - It is the 32bits version

2 - On an existing project, on a class diagramm:
  - select "Generalization" in toolbar
  - Then rightclick on a class object to open contextual menu
  - Select Duplicate in the contextual menu
  - Enjoy a crash !

3 - I've not tried it on version 2.21.80

-- 
You are receiving this mail because:
You are watching all bug changes.