On Thu, Mar 20, 2008 at 11:33 PM, Rinaldi J. Montessi <[EMAIL PROTECTED]> wrote: > > The gdb output I get is: > > > > Breakpoint 1, main (argc=0, argv=Cannot access memory at address 0x4) > > at pan.cc:280 > > I am not a coder. > > That line refers to work_pool which was the patch added for spawning a > new thread during uudecode. > > Why would an nzb do that? > > I do not use the nzb files so I have never seen this error. > > Rinaldi > -- > I brake for chezlogs! > > > > > _______________________________________________ > Pan-users mailing list > Pan-users@nongnu.org > http://lists.nongnu.org/mailman/listinfo/pan-users >
It's not from importing an nzb, like one you would download from an indexing site. If pan still has tasks in the queue when you exit, it creates a tasks.nzb file in the .pan2 directory, which it then loads on next start up. _______________________________________________ Pan-users mailing list Pan-users@nongnu.org http://lists.nongnu.org/mailman/listinfo/pan-users
