[exim-dev] [Bug 2904] "bad memory reference" errors in paniclog

2023-01-25 Thread admin--- via Exim-dev
https://bugs.exim.org/show_bug.cgi?id=2904

Jasen Betts  changed:

   What|Removed |Added

 CC||ja...@treshna.com

--- Comment #5 from Jasen Betts  ---
I encountered a bug like this, it was caused by log lines of 
exactly the wrong length and was fixed by commit
1ed24e36e279c922d3366f6c3144570cc5f54d7a 

Which will be in the next point release "4.97"

-- 
You are receiving this mail because:
You are on the CC list for the bug.
-- 
## List details at https://lists.exim.org/mailman/listinfo/exim-dev Exim 
details at http://www.exim.org/ ##


[exim-dev] [Bug 2904] "bad memory reference" errors in paniclog

2023-01-25 Thread admin--- via Exim-dev
https://bugs.exim.org/show_bug.cgi?id=2904

--- Comment #6 from Chance Rollins  ---
That is encouraging to hear.  Is there any estimated release timeline for 4.97?

Thank you very much Jasen.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
-- 
## List details at https://lists.exim.org/mailman/listinfo/exim-dev Exim 
details at http://www.exim.org/ ##


[exim-dev] [Bug 2904] "bad memory reference" errors in paniclog

2023-01-25 Thread admin--- via Exim-dev
https://bugs.exim.org/show_bug.cgi?id=2904

Jeremy Harris  changed:

   What|Removed |Added

 Resolution|--- |ALREADY_FIXED
 Status|REOPENED|RESOLVED

--- Comment #7 from Jeremy Harris  ---
No estimate, sorry.  It all depends on the rate changes accumulate.
We've only just gone over twenty ChangeLog entries for this cycle.

Given your reported version number (4.96-5), I guess you're using a
distro-built binary (not the same as the Exim project 4.96; but probably
that with some particular patches).  You could ask the distro maintainer to
cherry-pick that 1ed24e36e fix.

Or, if you're in a hurry, you could build from a git tree.

Meantime, I'll close this bug as "already fixed".
Thanks Jasen.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
-- 
## List details at https://lists.exim.org/mailman/listinfo/exim-dev Exim 
details at http://www.exim.org/ ##


[exim-dev] [Bug 2904] "bad memory reference" errors in paniclog

2023-01-24 Thread admin--- via Exim-dev
https://bugs.exim.org/show_bug.cgi?id=2904

Jeremy Harris  changed:

   What|Removed |Added

 Resolution|--- |WORKSFORME
 Status|NEW |RESOLVED

croll...@sjrollins.com changed:

   What|Removed |Added

 Status|RESOLVED|REOPENED
 Resolution|WORKSFORME  |---
 CC||croll...@sjrollins.com

--- Comment #2 from Jeremy Harris  ---
Closing due to lack of futer occurrence.  Please re-open if needed.

--- Comment #3 from croll...@sjrollins.com ---
I am currently on exim 4.96-5 and am experiencing this issue as well.  We have
been experiencing issues where messages being sent from an external system to
this exim server error out at times for unknown reasons since August 2022 and
we have now linked it back to this error message every time it happens.  I have
enabled +all logging and this is all that is provided.  There are no messages
between these two.  Ultimately the client connection is dropped.

2023-01-23 13:17:28.955 [126517] SMTP connection from [xxx.xxx.xxx.xxx]:52521
I=[xxx.xxx.xxx.xxx]:25 (TCP/IP connection count = 1)
2023-01-23 13:17:32.776 [201051] 1pK1Ns-000qIl-2N bad memory reference; pool
not found, at gstring_grow 1122

-- 
You are receiving this mail because:
You are on the CC list for the bug.
-- 
## List details at https://lists.exim.org/mailman/listinfo/exim-dev Exim 
details at http://www.exim.org/ ##


[exim-dev] [Bug 2904] "bad memory reference" errors in paniclog

2023-01-24 Thread admin--- via Exim-dev
https://bugs.exim.org/show_bug.cgi?id=2904

--- Comment #4 from croll...@sjrollins.com ---
As the error references gstring_grow function @ line 1122 I looked to see what
code changed there and found a change on 3/3/2022 which may be the cause.

February 6th 2022 Before -
https://github.com/Exim/exim/blob/dbab2d6f08acd5ccf71d5e8a6cdc1224ab857d7a/src/src/string.c

March 3rd 2022 After
https://github.com/Exim/exim/blob/4191cb150300d310ab5fa22ce2cfb02b6f6051b0/src/src/string.c

-- 
You are receiving this mail because:
You are on the CC list for the bug.
-- 
## List details at https://lists.exim.org/mailman/listinfo/exim-dev Exim 
details at http://www.exim.org/ ##


[exim-dev] [Bug 2904] "bad memory reference" errors in paniclog

2022-08-15 Thread admin--- via Exim-dev
https://bugs.exim.org/show_bug.cgi?id=2904

Git Commit  changed:

   What|Removed |Added

 CC||g...@exim.org

--- Comment #1 from Git Commit  ---
Git commit:
https://git.exim.org/exim.git/commitdiff/766af058762b2c4e21b69f335adf77265fe9509a

commit 766af058762b2c4e21b69f335adf77265fe9509a
Author: Jeremy Harris 
AuthorDate: Sat Aug 13 20:58:29 2022 +0100
Commit: Jeremy Harris 
CommitDate: Sun Aug 14 13:52:56 2022 +0100

Dump stack for "bad memory reference".  Bug 2904
---
 src/src/exim.c  | 2 +-
 src/src/functions.h | 1 +
 src/src/store.c | 3 +++
 3 files changed, 5 insertions(+), 1 deletion(-)

diff --git a/src/src/exim.c b/src/src/exim.c
index 23e206d..ea4286a 100644
--- a/src/src/exim.c
+++ b/src/src/exim.c
@@ -232,7 +232,7 @@ exit(1);
 ***/

 #define STACKDUMP_MAX 24
-static void
+void
 stackdump(void)
 {
 #ifndef NO_EXECINFO
diff --git a/src/src/functions.h b/src/src/functions.h
index e718234..92a4831 100644
--- a/src/src/functions.h
+++ b/src/src/functions.h
@@ -547,6 +547,7 @@ extern int stdin_ferror(void);
 extern BOOLstdin_hasc(void);
 extern int stdin_ungetc(int);

+extern voidstackdump(void);
 extern voidstore_exit(void);
 extern voidstore_init(void);
 extern voidstore_writeprotect(int);
diff --git a/src/src/store.c b/src/src/store.c
index c98fcbf..d99d2ab 100644
--- a/src/src/store.c
+++ b/src/src/store.c
@@ -274,6 +274,9 @@ for (pp = paired_pools; pp < paired_pools + N_PAIRED_POOLS;
pp++)
   for (b = pp->chainbase; b; b = b->next)
 if (is_pointer_in_block(b, p)) return pp;

+#ifndef COMPILE_UTILITY
+stackdump();
+#endif
 log_write(0, LOG_MAIN|LOG_PANIC_DIE,
   "bad memory reference; pool not found, at %s %d", func, linenumber);
 return NULL;

-- 
You are receiving this mail because:
You are on the CC list for the bug.
-- 
## List details at https://lists.exim.org/mailman/listinfo/exim-dev Exim 
details at http://www.exim.org/ ##