Re: my app segfault, but why?

[Ronald Bultje <rbultje ronald bitfreak net>]

On 2001.03.26 10:00:36 +0200 jean-françois BUTKIEWICZ wrote:
> Hi,
> 
> Most of SIGSEG dump-core case are based on a overflow. When it arrive, 
> it's very difficult to find quickly the error. You can check all yours 
> malloc, g_malloc and g_malloc0 (and other g_lib functions based on 
> memory allocations...) calls and see if all these call are terminated 
> with free, g_free ... Maybe you try to use g_free twice on the same vars 
> but allocated only one time ??.
> 
> Hope this can be helpfull.

My dumb thing is that one of my char[]'s was overflowed (stupid me).
I hope it's fixed now, I tested it and it didn't segfault this time :-).
Thanks for the help, next time I'll double check these things.

Ronald

-- 
---------------------------------------------------.
--   .-.    | Ronald Bultje                        |
--   /V\    | Running: Linux 2.4.2 and OpenBSD 2.8 |
--  // \\   | E-mail : rbultje ronald bitfreak net |
-- /(   )\  | WWW    : http://ronald.bitfreak.net/ |
--  ^^-^^   |    *** Warning: Unix Addicted ***    |
---------------------------------------------------'