Bug 146544 - valgrind segfaults when passing arguments to the launched command
Summary: valgrind segfaults when passing arguments to the launched command
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Fedora
Classification: Fedora
Component: valgrind
Version: rawhide
Hardware: All
OS: Linux
medium
high
Target Milestone: ---
Assignee: Jakub Jelinek
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2005-01-29 13:35 UTC by Bastien Nocera
Modified: 2007-11-30 22:10 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2005-05-03 09:23:09 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)

Description Bastien Nocera 2005-01-29 13:35:49 UTC 
/usr/bin/valgrind --tool=memcheck /usr/bin/gedit foo
*** glibc detected *** free(): invalid next size (normal): 0xb7dc07a0 ***
Aborted (core dumped)

The core is useless, and even running this inside gdb doesn't bring
much information. Removing the "foo" argument makes it work.

valgrind-2.2.0-7
kernel-2.6.10-1.741_FC3
Comment 1 Bastien Nocera 2005-02-07 14:35:14 UTC 
"valgrind --tool=memcheck /usr/bin/gedit" works
"valgrind -v --tool=memcheck /usr/bin/gedit" works
"valgrind -v --tool=memcheck /usr/bin/gedit foo" works

$ valgrind  --tool=memcheck /usr/bin/gedit foo
*** glibc detected *** free(): invalid next size (normal): 0xb7dc0770 ***
Aborted
Comment 2 Jakub Jelinek 2005-05-02 09:34:05 UTC 
Can you reproduce this with valgrind-2.4.0-2?
Comment 3 Bastien Nocera 2005-05-03 09:23:09 UTC 
Nope, can't. Thanks.
Note You need to log in before you can comment on or make changes to this bug.