Bug 118118

Summary:	Valgrind crashes with SIGBUS
Product:	[Developer tools] valgrind	Reporter:	Christoph Bartoschek <bartoschek>
Component:	memcheck	Assignee:	Julian Seward <jseward>
Status:	RESOLVED WORKSFORME
Severity:	normal	CC:	njn
Priority:	NOR	Keywords:	investigated, triaged
Version First Reported In:	3.1.0
Target Milestone:	---
Platform:	Unlisted Binaries
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Christoph Bartoschek 2005-12-11 16:22:07 UTC

After running our program for more than a day there is a crash with SIGBUS. 
Here are the messages: 
 
==01:02:38:32.373 2400== Warning: set address range perms: large range 
268439552, a 1, v 1 
==01:02:50:00.615 2400== Warning: set address range perms: large range 
268439552, a 0, v 0 
--01:02:52:57.936 2400-- INTERNAL ERROR: Valgrind received a signal 7 (SIGBUS) 
- exiting 
--01:02:52:57.936 2400-- si_code=2;  Faulting address: 0x4F4029EC;  sp: 
0x495A44610 
 
valgrind: the 'impossible' happened: 
   Killed by fatal signal 
==01:02:52:57.936 2400==    at 0x700C0FCD: disInstr_AMD64 (toIR.c:7954) 
==01:02:52:57.936 2400==    by 0x7008F238: bb_to_IR (bb_to_IR.c:187) 
==01:02:52:57.936 2400==    by 0x700688E5: LibVEX_Translate (vex_main.c:416) 
==01:02:52:57.936 2400==    by 0x7002354D: vgPlain_translate 
(libvex_basictypes.h:154) 
==01:02:52:57.936 2400==    by 0x70034759: handle_tt_miss (scheduler.c:596) 
==01:02:52:57.936 2400==    by 0x70034B81: vgPlain_scheduler (scheduler.c:717) 
==01:02:52:57.936 2400==    by 0x7004785E: thread_wrapper (syswrap-linux.c:86) 
==01:02:52:57.936 2400==    by 0x70047955: run_a_thread_NORETURN 
(syswrap-linux.c:119) 
==01:02:52:57.936 2400==    by 0x70047A86: vgModuleLocal_start_thread_NORETURN 
(syswrap-linux.c:206) 
==01:02:52:57.936 2400==    by 0x70050F2E: 
(within /usr/local/opt/x86_64-20050615/lib/valgrind/amd64-linux/memcheck) 
 
sched status: 
  running_tid=3

Comment 1 Julian Seward 2005-12-18 14:04:53 UTC

SIGBUS on non-riscs is usually a sign of accessing an area mmap'd
to a file, where the file is not long enough, and you are
accessing off the end of the file.

Can you re-run with --sanity-level=4 and see if it stops with
a report of any kind of memory management problem?  This will
make V run more slowly but lets us find certain kinds of 
problems which might be the root cause of this.

Comment 2 Christoph Bartoschek 2005-12-24 14:34:10 UTC

Ok, after some days of runtime I got:

--16041:0:aspacem  Valgrind: FATAL: M_PROCMAP_BUF is too low.
--16041:0:aspacem    Increase it and rebuild.  Exiting now.

I try to increase the value.

Comment 3 Julian Seward 2006-02-28 15:55:19 UTC

Christoph, any further info on this one?

Comment 4 Christoph Bartoschek 2006-02-28 19:51:30 UTC

Yes, after increasing the value valgrind does not crash any more.

Comment 5 Nicholas Nethercote 2009-07-01 09:04:26 UTC

I'm closing crashing and similar bugs that are more than two years old.  If
you still see this problem with Valgrind 3.4.1 please reopen the bug report.
Thanks.

Comment 6 Andrew Crouthamel 2018-09-19 04:36:19 UTC

Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!

Comment 7 Bug Janitor Service 2018-11-12 16:02:13 UTC

This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!