search for: parse_expression

Displaying 6 results from an estimated 6 matches for "parse_expression".

2005 Aug 01
4
valgrind complains about regex.c (PR#8043)
...algrind-2.2.0, a program supervision framework for= x86-linux. =3D=3D22324=3D=3D Copyright (C) 2000-2004, and GNU GPL'd, by Julian Seward = et al. =3D=3D22324=3D=3D For more details, rerun with: -v =3D=3D22324=3D=3D=20 =3D=3D22324=3D=3D Invalid read of size 4 =3D=3D22324=3D=3D at 0x81255AD: parse_expression (regex.c:5045) =3D=3D22324=3D=3D by 0x8125868: parse_branch (regex.c:4475) =3D=3D22324=3D=3D by 0x8125913: parse_reg_exp (regex.c:4420) =3D=3D22324=3D=3D by 0x81261B3: Rf_regcomp (regex.c:4384) =3D=3D22324=3D=3D Address 0x1C1E23A8 is 0 bytes after a block of size 32 a= lloc'd =3D=3D22...
2008 Jul 09
1
memory leak in sub("[range]",...)
...ointers to 7,915 not-freed blocks. ==32503== checked 12,616,568 bytes. ==32503== ==32503== 4 bytes in 1 blocks are possibly lost in loss record 1 of 45 ==32503== at 0x40046EE: malloc (vg_replace_malloc.c:149) ==32503== by 0x4005B9A: realloc (vg_replace_malloc.c:306) ==32503== by 0x80A5F92: parse_expression (regex.c:5202) ==32503== by 0x80A614F: parse_branch (regex.c:4707) ==32503== by 0x80A621A: parse_reg_exp (regex.c:4666) ==32503== by 0x80A6618: Rf_regcomp (regex.c:4635) ==32503== by 0x8110CB4: do_gsub (character.c:1355) ==32503== by 0x80654A4: do_internal (names.c:1135) ==32503==...
2017 Jun 21
6
RFC: Cleaning up the Itanium demangler
...ass C> const char* parse_encoding(const char* first, const char* last, C& db); template <class C> const char* parse_name(const char* first, const char* last, C& db, bool* ends_with_template_args = 0); template <class C> const char* parse_expression(const char* first, const char* last, C& db); template <class C> const char* parse_template_args(const char* first, const char* last, C& db); template <class C> const char* parse_operator_name(const char* first, const char* last, C& db); template <class C>...
2008 Aug 07
1
memory leak in sub("[range]", ...) when #ifndef _LIBC (PR#11946)
...966) ==28643== by 0x80566B5: main (Rmain.c:33) ==28643== ==28643== ==28643== 7,996 bytes in 1,999 blocks are definitely lost in loss record 35 of 44 ==28643== at 0x40046EE: malloc (vg_replace_malloc.c:149) ==28643== by 0x4005B9A: realloc (vg_replace_malloc.c:306) ==28643== by 0x80A5E22: parse_expression (regex.c:5202) ==28643== by 0x80A5FDF: parse_branch (regex.c:4707) ==28643== by 0x80A60AA: parse_reg_exp (regex.c:4666) ==28643== by 0x80A64A8: Rf_regcomp (regex.c:4635) ==28643== by 0x8110AE0: do_gsub (character.c:1355) ==28643== by 0x80653BC: do_internal (names.c:1129) ==28643==...
2008 Aug 07
0
memory leak in sub("[range]", ...) when #ifndef _LIBC (PR#12488)
...n (Rmain.c:33) > ==28643== > ==28643== > ==28643== 7,996 bytes in 1,999 blocks are definitely lost in loss record 35 of > 44 > ==28643== at 0x40046EE: malloc (vg_replace_malloc.c:149) > ==28643== by 0x4005B9A: realloc (vg_replace_malloc.c:306) > ==28643== by 0x80A5E22: parse_expression (regex.c:5202) > ==28643== by 0x80A5FDF: parse_branch (regex.c:4707) > ==28643== by 0x80A60AA: parse_reg_exp (regex.c:4666) > ==28643== by 0x80A64A8: Rf_regcomp (regex.c:4635) > ==28643== by 0x8110AE0: do_gsub (character.c:1355) > ==28643== by 0x80653BC: do_internal (n...
2008 Jul 10
0
RODBC Close Memory Leak Question
...(eval.c:507) ==8682== by 0x818631E: do_begin (eval.c:1172) ==8682== ==8682== ==8682== 56 bytes in 14 blocks are definitely lost in loss record 16 of 55 ==8682== at 0x40051F9: malloc (vg_replace_malloc.c:149) ==8682== by 0x4005271: realloc (vg_replace_malloc.c:306) ==8682== by 0x80B47EC: parse_expression (regex.c:5202) ==8682== by 0x80B4934: parse_branch (regex.c:4714) ==8682== by 0x80B49BF: parse_reg_exp (regex.c:4666) ==8682== by 0x80B5317: Rf_regcomp (regex.c:4635) ==8682== by 0x812A38F: do_gsub (character.c:1356) ==8682== by 0x806650A: do_internal (names.c:1129) ==8682== by 0x...