Re: [fpc-pascal] How to analyze a core dump?

2007-06-30 Thread Luca Olivetti
En/na Luca Olivetti ha escrit: Maybe it's not a good idea to mix c multithreaded libraries and pascal code? Any special unit I should use? (I already tried cmem and it made no difference). If I cannot solve it I think I'll have to write a small backend program in c that communicates with

Re: [fpc-pascal] How to analyze a core dump?

2007-06-27 Thread Vinzent Hoefler
On Wednesday 27 June 2007 07:55, Jonas Maebe wrote: On 27 jun 2007, at 08:13, Vinzent Hoefler wrote: There also seemed to be some issues with the reference counting: if I passed a local AnsiString to a thread constructor as argument and left the routine then, this seemed to confuse the

Re: [fpc-pascal] How to analyze a core dump?

2007-06-27 Thread Jonas Maebe
On 27 jun 2007, at 08:47, Vinzent Hoefler wrote: In that case, the refcount of the ansistring you pass isn't increased, Meaning that the string will be freed once I leave the routine that called the constructor? Yes. Jonas ___ fpc-pascal

Re: [fpc-pascal] How to analyze a core dump?

2007-06-27 Thread Luca Olivetti
En/na Vinzent Hoefler ha escrit: On Tuesday 26 June 2007 17:26, Luca Olivetti wrote: procedure TButlerPhone.Receive(s: string); so s is a parameter. This procedure is called exclusively from procedure TStatusThread.Receive; begin FOwner.Receive(FData) end; (FOwner is a TButlerPhone)

Re: [fpc-pascal] How to analyze a core dump?

2007-06-27 Thread Luca Olivetti
En/na Vincent Snijders ha escrit: On Wed, 27 Jun 2007 19:38:03 +0200 Luca Olivetti [EMAIL PROTECTED] wrote: En/na Luca Olivetti ha escrit: En/na Cesar Romero ha escrit: Where S is initialized? I only see L initialized. []s Cesar Romero 442: L:=length(s); 443: if L1 then exit; 444:

Re: [fpc-pascal] How to analyze a core dump?

2007-06-26 Thread Luca Olivetti
En/na Tom Walsh ha escrit: Nope, it is 'gdb -c corefilename'. Sorry :-( Been there, done that, got the t-shirt. http://article.gmane.org/gmane.comp.compilers.free-pascal.general/8211 thanks for trying. -- Luca ___ fpc-pascal maillist -

Re: [fpc-pascal] How to analyze a core dump?

2007-06-26 Thread Jonas Maebe
On 25 jun 2007, at 22:44, Luca Olivetti wrote: En/na Jonas Maebe ha escrit: On 14 jun 2007, at 19:04, Luca Olivetti wrote: No suggestions? Is there some special option (apart from -g) that I should specify to compile/link my program? No. But the garbage backtrace means that either your gdb

Re: [fpc-pascal] How to analyze a core dump?

2007-06-26 Thread Luca Olivetti
En/na Jonas Maebe ha escrit: On 25 jun 2007, at 22:44, Luca Olivetti wrote: En/na Jonas Maebe ha escrit: On 14 jun 2007, at 19:04, Luca Olivetti wrote: No suggestions? Is there some special option (apart from -g) that I should specify to compile/link my program? No. But the garbage

Re: [fpc-pascal] How to analyze a core dump?

2007-06-26 Thread Cesar Romero
Where S is initialized? I only see L initialized. []s Cesar Romero 442: L:=length(s); 443: if L1 then exit; 444: case s[1] of so I can't see how it could possibly be uninitialized. Bye ___ fpc-pascal maillist -

Re: [fpc-pascal] How to analyze a core dump?

2007-06-26 Thread Luca Olivetti
En/na Cesar Romero ha escrit: Where S is initialized? I only see L initialized. []s Cesar Romero 442: L:=length(s); 443: if L1 then exit; 444: case s[1] of so I can't see how it could possibly be uninitialized. nothwithstanding the fact that if length(s)1 line 444 won't be executed,

Re: [fpc-pascal] How to analyze a core dump?

2007-06-25 Thread Luca Olivetti
En/na Jonas Maebe ha escrit: On 14 jun 2007, at 19:04, Luca Olivetti wrote: No suggestions? Is there some special option (apart from -g) that I should specify to compile/link my program? No. But the garbage backtrace means that either your gdb cannot parse the signal handler frame, or that

Re: [fpc-pascal] How to analyze a core dump?

2007-06-25 Thread Tom Walsh
Luca Olivetti wrote: En/na Jonas Maebe ha escrit: On 14 jun 2007, at 19:04, Luca Olivetti wrote: No suggestions? Is there some special option (apart from -g) that I should specify to compile/link my program? No. But the garbage backtrace means that either your gdb cannot parse the signal

Re: [fpc-pascal] How to analyze a core dump?

2007-06-14 Thread Luca Olivetti
En/na Luca Olivetti ha escrit: Hello, I'm trying to debug a segment violation, I compiled the program with -g, but analyzing the core dump isn't really helpful, maybe the warning can't read pathname for load map is the cause? Or it's possible that it's caused by some of the c libraries used

Re: [fpc-pascal] How to analyze a core dump?

2007-06-14 Thread Jonas Maebe
On 14 jun 2007, at 19:04, Luca Olivetti wrote: No suggestions? Is there some special option (apart from -g) that I should specify to compile/link my program? No. But the garbage backtrace means that either your gdb cannot parse the signal handler frame, or that your program corrupted the

[fpc-pascal] How to analyze a core dump?

2007-06-10 Thread Luca Olivetti
Hello, I'm trying to debug a segment violation, I compiled the program with -g, but analyzing the core dump isn't really helpful, maybe the warning can't read pathname for load map is the cause? Or it's possible that it's caused by some of the c libraries used having no debug symbols? Any

Re: [fpc-pascal] How to analyze a core dump?

2007-06-10 Thread John Coppens
On Sun, 10 Jun 2007 21:30:09 +0200 Luca Olivetti [EMAIL PROTECTED] wrote: I'm trying to debug a segment violation, I compiled the program with -g, but analyzing the core dump isn't really helpful, maybe the warning can't read pathname for load map is the cause? Or it's possible that it's

Re: [fpc-pascal] How to analyze a core dump?

2007-06-10 Thread Luca Olivetti
En/na John Coppens ha escrit: On Sun, 10 Jun 2007 21:30:09 +0200 Luca Olivetti [EMAIL PROTECTED] wrote: I'm trying to debug a segment violation, I compiled the program with -g, but analyzing the core dump isn't really helpful, maybe the warning can't read pathname for load map is the cause? Or

Re: [fpc-pascal] How to analyze a core dump?

2007-06-10 Thread ik
Hi, On 6/10/07, Luca Olivetti [EMAIL PROTECTED] wrote: Hello, I'm trying to debug a segment violation, I compiled the program with -g, but analyzing the core dump isn't really helpful, maybe the warning can't read pathname for load map is the cause? Or it's possible that it's caused by some of