|
|
sybperl-l Archive
Up Prev Next
From: Michael Peppler <mpeppler at peppler dot org>
Subject: RE: Problem with sybperl
Date: Jun 19 2002 7:15PM
On Wed, 2002-06-19 at 11:53, Sabherwal, Balvinder (MBS) wrote:
> here is the stack information
>
> wpsdb01 /opt/sybasescripts/DB_Admin $gdb `which perl` core
> GNU gdb 4.17
> #0 0xef5a4734 in strlen ()
> (gdb) bt
> #0 0xef5a4734 in strlen ()
> #1 0xef49a454 in newdbh ()
> #2 0xef4a5db8 in XS_Sybase__CTlib_ct_connect ()
That is really weird!
Could you please edit CTlib/Makefile and add -g to either the CCFLAGS or
OPTIMIZE macro, and then rm CTlib.o and run make again (so that debug
symbols are included).
Now run your script again, and do send me the stacktrace (which should
now include line numbers).
Also - what version of sybperl do you have?
Michael
> -----Original Message-----
> From: Michael Peppler [mailto:mpeppler@peppler.org]
> Sent: Wednesday, June 19, 2002 1:41 PM
> To: SybPerl Discussion List
> Subject: RE: Problem with sybperl
>
>
> On Wed, 2002-06-19 at 10:27, Sabherwal, Balvinder (MBS) wrote:
> >
> > >Off hand it's hard to say what could be wrong.
> > >
> > >If you have a debugger installed (gdb or dbx) it may help to get a stack
> > >trace. In gdb:
> > >
> > >prompt> gdb `which perl` core
> > >(gdb) bt
> >
> > >This will normally list where the segmentation fault occured, and the
> > >call stack.
> >
> > tried gdb but it doesn't recognizes the format of the core file and I do
> not
> > have the dbx. any thing else I can try??
>
> Hmmm - that probably means that the gdb binary is too old for your
> platform.
>
> Try downloading a more recent one from www.sunfreeware.com
>
> Michael
> --
> Michael Peppler / mpeppler@peppler.org / http://www.mbay.net/~mpeppler
> mpeppler@zetatools.com / ZetaTools, Inc / http://www.zetatools.com
> ZetaTools: Call perl functions as Sybase stored procedures!
>
--
Michael Peppler / mpeppler@peppler.org / http://www.mbay.net/~mpeppler
mpeppler@zetatools.com / ZetaTools, Inc / http://www.zetatools.com
ZetaTools: Call perl functions as Sybase stored procedures!
|
