Citeren Charles Lepple <[email protected]>:
>> This is strange. I have no debugging info but i built it with -g , but it
>> would
>> not give me anything but ??:0 as output. So i built it with -gstabs, and
>> guess what.... it does not segfault.
> Well, it sort of sounds like it might be related to the compiler -
> using a different debugging option shouldn't change how the code is
> generated, unless it isn't optimizing as much with -gstabs.
Another thing to try is to run it through valgrind. This works best if
you switch of optimization ('-O0', which should be read as -O<zero>),
but usually will also give usable info with optimized code ('-O2' or
even 'O3') as well.
Best regards, Arjen
--
Please keep list traffic on the list
_______________________________________________
Nut-upsdev mailing list
[email protected]
http://lists.alioth.debian.org/mailman/listinfo/nut-upsdev
