On Monday 10 August 2009 03:14:26 Dan Langille wrote:
> Kern Sibbald wrote:
> > On Sunday 09 August 2009 20:44:03 Dan Langille wrote:
> >> Kern Sibbald wrote:
> >>> On Sunday 09 August 2009 17:31:04 Dan Langille wrote:
> >>>> FYI: this came up on my first git run. No idea why.
> >>>
> >>> Well the first thing would be to find out why gdb says that your source
> >>> and binary do not agree.  Fixing that will probably fix the problem
> >>
> >> Did a fresh run.  Same problem.
> >>
> >> Not sure why this occurs: 'Variable "exelen" is not available'
> >>
> >> You say it's source != binary.  Given a fresh run, how can that happen?
> >
> > I don't know the answer. You are doing the build.
> >
> > If the binary and source don't correspond as gdb says, then the "build"
> > is broken or you are not executing the binary you think you are.
>
> These are the regression tests.  That's all I'm running:

Dan:
The first thing is to update to the current git, then try again (there was for 
a short time a build error that crept into the repo).  If it fails again, 
then you should manually build with "make setup" and ensure there are no 
build errors.  If there are, I need to see them.  If make setup works, then 
try manually running one of the tests.  If it fails, you will need to 
manually run the FD under the debugger to get a good traceback -- traceback 
below is not very useful.  It doesn't make a lot of sense, unless it is 
recursing -- i.e. it got a seg fault, then in the automatic traceback 
handler, it got another seg fault.  Such cases are unusual, and the solution 
is to manually run the debugger so that you catch it at the first crash and 
manually produce the traceback.

Frank:
The first step is sending me the traceback.  I see from the nightly 
regressions that your tests seem to be working, so it will be interesting. If 
your traceback looks the same as Dan's then I'll either wait to see what Dan 
comes up with or ask you to try the same procedure I recommend above.

Thanks to both of you for running the regression scripts. It is *really* 
useful to find these kinds of problems early.

Kern

>
>
> cd  ~/src/BaculaRegressionTesting-TRUNK
> git pull
> cd regress
> ./nightly-disk
>
> >>> Kern
> >>>
> >>>> --
> >>>> Dan Langille
> >>>> http://langille.org/
> >>>>
> >>>> Begin forwarded message:
> >>>>> From: dan
> >>>>> Date: August 9, 2009 11:18:13 AM EDT
> >>>>> To: dan
> >>>>> Subject: Bacula GDB traceback of bacula-fd on polo.example.org
> >>>>>
> >>>>>
> >>>>> [New Thread 0x8019020b0 (LWP 100095)]
> >>>>> [Switching to Thread 0x8019020b0 (LWP 100095)]
> >>>>> 0x000000080165c0aa in wait4 () from /lib/libc.so.7
> >>>>> $1 = '\0' <repeats 29 times>
> >>>>> $2 = 0x801909068 "bacula-fd"
> >>>>> $3 = 0x80190a0a8 "/usr/home/dan/src/BaculaRegressionTesting-TRUNK/
> >>>>> regress/bin/bacula-fd"
> >>>>> $4 = 0x0
> >>>>> $5 = 0x800ab8452 "3.0.3 (09 August 2009)"
> >>>>> $6 = 0x800ab8469 "x86_64-unknown-freebsd7.2"
> >>>>> $7 = 0x800ab8483 "freebsd"
> >>>>> $8 = 0x800ab848b "7.2-STABLE"
> >>>>> $9 = "polo.example.org", '\0' <repeats 30 times>
> >>>>> #0  0x000000080165c0aa in wait4 () from /lib/libc.so.7
> >>>>> #1  0x0000000800bce11e in waitpid () from /lib/libthr.so.3
> >>>>> #2  0x0000000800aa7eb2 in signal_handler (sig=11) at signal.c:211
> >>>>> #3  <signal handler called>
> >>>>> #4  0x0000000000407c8c in terminate_filed (sig=1) at filed.c:282
> >>>>> #5  0x000000000040851c in main (argc=0, argv=Variable "argv" is not
> >>>>> available.
> >>>>> ) at filed.c:210
> >>>>>
> >>>>> Thread 1 (Thread 0x8019020b0 (LWP 100095)):
> >>>>> #0  0x000000080165c0aa in wait4 () from /lib/libc.so.7
> >>>>> #1  0x0000000800bce11e in waitpid () from /lib/libthr.so.3
> >>>>> #2  0x0000000800aa7eb2 in signal_handler (sig=11) at signal.c:211
> >>>>> #3  <signal handler called>
> >>>>> #4  0x0000000000407c8c in terminate_filed (sig=1) at filed.c:282
> >>>>> #5  0x000000000040851c in main (argc=0, argv=Variable "argv" is not
> >>>>> available.
> >>>>> ) at filed.c:210
> >>>>> #0  0x000000080165c0aa in wait4 () from /lib/libc.so.7
> >>>>> No symbol table info available.
> >>>>> #1  0x0000000800bce11e in waitpid () from /lib/libthr.so.3
> >>>>> No symbol table info available.
> >>>>> #2  0x0000000800aa7eb2 in signal_handler (sig=11) at signal.c:211
> >>>>> warning: Source file is more recent than executable.
> >>>>>
> >>>>> 211             waitpid(pid, NULL, 0);       /* wait for child to
> >>>>> produce dump */
> >>>>> Current language:  auto; currently c++
> >>>>> sigdefault = {__sigaction_u = {__sa_handler = 0, __sa_sigaction = 0},
> >>>>>  sa_flags = 0, sa_mask = {__bits = {4294967295, 4294967295,
> >>>>> 4294967295,
> >>>>>      4294967295}}}
> >>>>> buf = "/tmp/\000\000\000\000\004", '\0' <repeats 14 times>, "\237}ú\
> >>>>> 000\b\000\000\000¸ÊÝñ\006\0343Kd~\231µÒð\017/@Rey\216¤»Óì
> >>>>> \006!=Zx\227·ÈÚí\001\026,C[t\216©Åâ\000\037?Pbu\211\236´Ëãü
> >>>>> \0261Mj\210§ÇØêý\021"
> >>>>> pid = 52783
> >>>>> exelen = /usr/home/dan/src/BaculaRegressionTesting-TRUNK/regress/bin/
> >>>>> btraceback.gdb:17: Error in sourced command file:
> >>>>> Variable "exelen" is not available.
>
> ---------------------------------------------------------------------------
>--- Let Crystal Reports handle the reporting - Free Crystal Reports 2008
> 30-Day trial. Simplify your report design, integration and deployment - and
> focus on what you do best, core application coding. Discover what's new
> with Crystal Reports now.  http://p.sf.net/sfu/bobj-july
> _______________________________________________
> Bacula-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/bacula-devel



------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
Bacula-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bacula-devel

Reply via email to