> Hmm, this doesn't sound like it's going to be simple to fix in > a clean way. > > For the moment, can we do the incremental fix of taking Philippe's > patch (with the off-by-one fixed) ? That's a very simple patch > and uncontroversial patch. (Maybe should also backport it for > 3.7.1 ?)
Sounds good to me. This is still a big improvement. > At work, a user is doing a nasty trick to survive in such a case: he > writes a suppression file for all errors preceeding the one he is > interested in. Not very easy but can be made better > by having a new command line option: > --vgdb-error-list=<filename> invoke gdbserver for each error described > in filename > > The big advantage of this schema is that it is not sensitive > to scheduling/numbering/... > > With this, gdbserver would be invoked either when the error nr is>= > --vgdb-error > or when it matches an error described in --vgdb-error-list. > The --vgdb-error-list=<filename> will use the same format as a suppression > file. > Even better! I think this is a good combination of options and should suit most eventualities. thanks, Rob ------------------------------------------------------------------------------ Keep Your Developer Skills Current with LearnDevNow! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-d2d _______________________________________________ Valgrind-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/valgrind-users
