https://bugs.kde.org/show_bug.cgi?id=397424
--- Comment #8 from Philippe Waroquiers <philippe.waroqui...@skynet.be> ---
(In reply to Dimitrije Nikolic from comment #5)
Finally replying, after some holidays ;).
> Created attachment 114443 [details]
> glibc2-27 & gdbserver problem v3
>
> I was trying for a few days to solve this problem like you suggested (before
> sending first patch), but it's too complicated to make sed expression which
> will filter all possible outputs result on the same way. There are too many
> differences between versions of glibc and platforms.
Yes, all these differences are very painful (and these differences
are the reasons why we already have about 60 sed expressions
in filter_gdb).
It is not very clear to me why the output of glibc 2-27 cannot
be handled similarly to the other differences we had up to now.
Can you clarify this by showing an (unfiltered) stacktrace
produced by glibc 2-27 ?
(e.g. attach the unfiltered output of mcinfcallWSRU obtained by
running the test with --keep-unfiltered).
Otherwise, if we reach the conclusion that the 'start/end delete'
technique is the best, I think we already have this technique
supported in filter_gdb via:
-e '/filter_gdb BEGIN drop/,/filter_gdb END drop/d'
\
>
> For mcmain_pic: I removed added exp file, and added filter_mcmain which
> replace number of bytes and blocks to "xx".
As I do not believe that we have any need to check the 'in use at exit'
in any vgdb tests, I think we better do the sed expression to change
in use at exit: [0-9][0-9]* bytes in [0-9][0-9]* blocks
to
in use at exit: ... bytes in ... blocks
as part of filter_gdb.
If you prefer, you can do this part as a separate first patch.
Thanks for the patience ...
--
You are receiving this mail because:
You are watching all bug changes.
