|
From: Steve A. <st...@bl...> - 2004-09-01 02:58:24
|
When running valgrind --tool=massif on some code compiled with -g using gcc 2.95, dynamically linked with a bunch of libraries valgrind throws this at startup: ==21540== Massif, a space profiler for x86-linux. ==21540== Copyright (C) 2003, Nicholas Nethercote ==21540== Using valgrind-2.2.0, a program supervision framework for x86-linux. ==21540== Copyright (C) 2000-2004, and GNU GPL'd, by Julian Seward et al. @@ unlikely looking definition in unparsed remains ";" @@ unlikely looking definition in unparsed remains ";" @@ unlikely looking definition in unparsed remains ";" @@ unlikely looking definition in unparsed remains ";" @@ unlikely looking definition in unparsed remains ";" @@ unlikely looking definition in unparsed remains ";" @@ unlikely looking definition in unparsed remains ";" @@ unlikely looking definition in unparsed remains ";" @@ unlikely looking definition in unparsed remains ";" ==21540== For more details, rerun with: -v ==21540== @@ unlikely looking definition in unparsed remains ";" @@ unlikely looking definition in unparsed remains ";" @@ unlikely looking definition in unparsed remains ";" @@ unlikely looking definition in unparsed remains ";" @@ unlikely looking definition in unparsed remains ";" @@ unlikely looking definition in unparsed remains ";" @@ unlikely looking definition in unparsed remains ";" @@ unlikely looking definition in unparsed remains ";" I'm guessing there's something hinky with the stabs parsing. Any guesses as to where I should look? Cheers, Steve |
|
From: Nicholas N. <nj...@ca...> - 2004-09-01 21:51:46
|
On Tue, 31 Aug 2004, Steve Atkins wrote: > When running valgrind --tool=massif on some code compiled with -g > using gcc 2.95, dynamically linked with a bunch of libraries > valgrind throws this at startup: > > ==21540== Massif, a space profiler for x86-linux. > ==21540== Copyright (C) 2003, Nicholas Nethercote > ==21540== Using valgrind-2.2.0, a program supervision framework for x86-linux. > ==21540== Copyright (C) 2000-2004, and GNU GPL'd, by Julian Seward et al. > @@ unlikely looking definition in unparsed remains ";" > > I'm guessing there's something hinky with the stabs parsing. Any guesses > as to where I should look? Do you mean, how to fix it? I guess you need to work out what ";" means in that context in stabs, and decide how to deal with it. (Ignoring it might be the right thing to do, that's how ":" is handled, for example.) Google for the stabs docs if you're keen. And can you file a bug report for this, please? (See valgrind.kde.org/bugs.html) Thanks. N |
|
From: Nicholas N. <nj...@ca...> - 2004-09-02 14:23:24
|
On Tue, 31 Aug 2004, Steve Atkins wrote: > When running valgrind --tool=massif on some code compiled with -g > using gcc 2.95, dynamically linked with a bunch of libraries > valgrind throws this at startup: > > ==21540== Massif, a space profiler for x86-linux. > ==21540== Copyright (C) 2003, Nicholas Nethercote > ==21540== Using valgrind-2.2.0, a program supervision framework for x86-linux. > ==21540== Copyright (C) 2000-2004, and GNU GPL'd, by Julian Seward et al. > @@ unlikely looking definition in unparsed remains ";" > @@ unlikely looking definition in unparsed remains ";" > @@ unlikely looking definition in unparsed remains ";" > @@ unlikely looking definition in unparsed remains ";" > @@ unlikely looking definition in unparsed remains ";" > @@ unlikely looking definition in unparsed remains ";" > @@ unlikely looking definition in unparsed remains ";" > @@ unlikely looking definition in unparsed remains ";" > @@ unlikely looking definition in unparsed remains ";" > ==21540== For more details, rerun with: -v > ==21540== > @@ unlikely looking definition in unparsed remains ";" > @@ unlikely looking definition in unparsed remains ";" > @@ unlikely looking definition in unparsed remains ";" > @@ unlikely looking definition in unparsed remains ";" > @@ unlikely looking definition in unparsed remains ";" > @@ unlikely looking definition in unparsed remains ";" > @@ unlikely looking definition in unparsed remains ";" > @@ unlikely looking definition in unparsed remains ";" > > I'm guessing there's something hinky with the stabs parsing. Any guesses > as to where I should look? Oh, I guess this hangs after it's printed these messages? If so, it looks like the same bug as Naveen Kumar just mentioned. Can one of you file a bug in Bugzilla, please? N |
|
From: Steve A. <st...@bl...> - 2004-09-02 15:44:40
|
On Thu, Sep 02, 2004 at 03:23:20PM +0100, Nicholas Nethercote wrote: > >When running valgrind --tool=massif on some code compiled with -g > >using gcc 2.95, dynamically linked with a bunch of libraries > >valgrind throws this at startup: > > [snip] > > @@ unlikely looking definition in unparsed remains ";" > > @@ unlikely looking definition in unparsed remains ";" > > > >I'm guessing there's something hinky with the stabs parsing. Any guesses > >as to where I should look? > > Oh, I guess this hangs after it's printed these messages? If so, it looks No, it runs fine after that, and the data it displays appears valid. > like the same bug as Naveen Kumar just mentioned. Can one of you file a > bug in Bugzilla, please? BUG# 88703 added. Cheers, Steve |