[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: gnokii --send-sms core dumps

From: Jan Derfinak
Subject: Re: gnokii --send-sms core dumps
Date: Sat, 1 Dec 2012 21:09:36 +0100 (CET)
User-agent: Alpine 2.00 (LNX 1167 2008-08-23)

On Fri, 30 Nov 2012, ML mail wrote:

> Thanks, I now managed to compile gnokii from the git source with your
> instructions. Unfortunately, smsd does a segmentation fault like before
> using the latest stable version of gnokii. Just now gdb mentions another
> line but it's still an opening curly brace as you can see in the output
> below:

Please try to remove any -O* options when compiling gnokii. Were there any
warnings during compilation? Was the -Wall option used?


> ____________________________________________________________________________
> From: Daniele Forsi <address@hidden>
> To: ML mail <address@hidden>
> Cc: Discussion forum for gnokii users. <address@hidden>
> Sent: Friday, November 30, 2012 3:28 PM
> Subject: Re: gnokii --send-sms core dumps
> 2012/11/30 ML mail <address@hidden>:
> > Was just wondering if someone of you had a clue why my smsd is still core
> > dumping? All the details are in my mail below...
> sorry for not getting back to you
> I have ho idea why it would segfault on the opening brace here:
> > Program received signal SIGSEGV, Segmentation fault.
> > [Switching to process 5507, thread 0x8904fc00]
> > 0x01944f9f in Functions (op=GN_OP_Init, data=0x0, state=0x8bc79000) at
> > nk6100.c:232
> > 232    {
> the most probable cause is that the sources don't match the
> executable, so that line 232 has a different content, can you check if
> the smsd you are running is actually built from the source files whose
> lines that are printed by gdb? gdb prints a warning f the sources are
> newer than the executable but it doens't seem your case. You can also
> try to compile the sources from git which is what I'm actually using;
> for instructions see
> > if you need more details
> > don't hesitate to ask me. I would really be happy to be able to use smsd
> on
> > my OpenBSD box.
> you can also try to run under valgrind because it could be able to
> show if smsd is accessing memory that it shouldn't (invalid write),
> smsd will run slower but it's a quick test:
> valgrind /usr/local/gnokii/bin/smsd -u smsd -p PASSWORD -d smsd -m
> mysql -f /tmp/smsd.log
> --
> Daniele Forsi


reply via email to

[Prev in Thread] Current Thread [Next in Thread]